From 9d5ab09a6f487a43b5363773b6a493285777102d Mon Sep 17 00:00:00 2001
From: Chirag0002
Date: Thu, 23 Mar 2023 00:39:56 +0530
Subject: [PATCH 001/446] removed duplicated examples
---
.../pods-and-endpoint-termination-flow.md | 50 ++-----------------
.../explore-graceful-termination-nginx.yaml | 11 ++++
2 files changed, 16 insertions(+), 45 deletions(-)
create mode 100644 content/en/examples/service/explore-graceful-termination-nginx.yaml
diff --git a/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md
index 2d812f9ddc..469a34a7ee 100644
--- a/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md
+++ b/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md
@@ -38,53 +38,13 @@ Let's say you have a Deployment containing of a single `nginx` replica
{{< codenew file="service/pod-with-graceful-termination.yaml" >}}
-```yaml
-apiVersion: apps/v1
-kind: Deployment
-metadata:
- name: nginx-deployment
- labels:
- app: nginx
-spec:
- replicas: 1
- selector:
- matchLabels:
- app: nginx
- template:
- metadata:
- labels:
- app: nginx
- spec:
- terminationGracePeriodSeconds: 120 # extra long grace period
- containers:
- - name: nginx
- image: nginx:latest
- ports:
- - containerPort: 80
- lifecycle:
- preStop:
- exec:
- # Real life termination may take any time up to terminationGracePeriodSeconds.
- # In this example - just hang around for at least the duration of terminationGracePeriodSeconds,
- # at 120 seconds container will be forcibly terminated.
- # Note, all this time nginx will keep processing requests.
- command: [
- "/bin/sh", "-c", "sleep 180"
- ]
+{{< codenew file="service/explore-graceful-termination-nginx.yaml" >}}
----
+Now create the Deployment Pod and Service using the above files:
-apiVersion: v1
-kind: Service
-metadata:
- name: nginx-service
-spec:
- selector:
- app: nginx
- ports:
- - protocol: TCP
- port: 80
- targetPort: 80
+```shell
+kubectl apply -f pod-with-graceful-termination.yaml
+kubectl apply -f explore-graceful-termination-nginx.yaml
```
Once the Pod and Service are running, you can get the name of any associated EndpointSlices:
diff --git a/content/en/examples/service/explore-graceful-termination-nginx.yaml b/content/en/examples/service/explore-graceful-termination-nginx.yaml
new file mode 100644
index 0000000000..6d1f97a64d
--- /dev/null
+++ b/content/en/examples/service/explore-graceful-termination-nginx.yaml
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: Service
+metadata:
+ name: nginx-service
+spec:
+ selector:
+ app: nginx
+ ports:
+ - protocol: TCP
+ port: 80
+ targetPort: 80
\ No newline at end of file
From 2691061e9ea948ac1f9c671f21d8953a69f141bb Mon Sep 17 00:00:00 2001
From: Amol Mote
Date: Mon, 28 Nov 2022 20:48:21 +0530
Subject: [PATCH 002/446] [hi] Localize
content/hi/docs/reference/glossary/job.md
Signed-off-by: Amol Mote
---
content/hi/docs/reference/glossary/job.md | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100644 content/hi/docs/reference/glossary/job.md
diff --git a/content/hi/docs/reference/glossary/job.md b/content/hi/docs/reference/glossary/job.md
new file mode 100644
index 0000000000..a52140092d
--- /dev/null
+++ b/content/hi/docs/reference/glossary/job.md
@@ -0,0 +1,19 @@
+---
+title: जॉब (Job)
+id: job
+date: 2018-04-12
+full_link: /docs/concepts/workloads/controllers/job/
+short_description: >
+ एक परिमित या बैच कार्य जो पूरा होने तक चलता है।
+
+aka:
+tags:
+- fundamental
+- core-object
+- workload
+---
+ एक परिमित या बैच कार्य जो पूरा होने तक चलता है।
+
+
+
+जॉब एक या अधिक {{}} ऑब्जेक्ट बनाता है और सुनिश्चित करता है कि उनमें से एक निर्दिष्ट संख्या सफलतापूर्वक समाप्त हो जाए। जैसे ही पॉड्स सफलतापूर्वक पूर्ण होते हैं, जॉब उस सफल समापन को ट्रैक करता है।
\ No newline at end of file
From ef075496bf15002334dcf41b6e21fa216f6aa3fe Mon Sep 17 00:00:00 2001
From: NitishKumar06
Date: Sun, 25 Dec 2022 18:38:01 +0530
Subject: [PATCH 003/446] Modified hi.toml to adopt new localization string for
release page
---
data/i18n/hi/hi.toml | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/data/i18n/hi/hi.toml b/data/i18n/hi/hi.toml
index c63259c557..a8ec25549d 100644
--- a/data/i18n/hi/hi.toml
+++ b/data/i18n/hi/hi.toml
@@ -1,6 +1,13 @@
# i18n strings for Hindi version of the site.
# NOTE: Please keep the entries in alphabetical order when editing
+# Avoid using conjunction_1.
+# Must match the context in layouts/shortcodes/release-data.html
+# Appears on https://kubernetes.io/releases/
+# For example the "and" in "Complete 1.25 Schedule and Changelog"
+[conjunction_1]
+other = "और"
+
[caution]
other = "सावधानी:"
@@ -240,6 +247,21 @@ other = "(रिलीज़ड: "
[release_date_format]
other = "2006-01-02"
+# Deprecated. Planned for removal in a future release.
+# Use [release_full_details_initial_text] instead.
+[release_complete]
+other = "पूर्ण"
+
+# Replace [release_complete] with [release_full_details_initial_text]
+[release_full_details_initial_text]
+other = "पूर्ण"
+
+[release_schedule]
+other = "अनुसूची"
+
+[release_changelog]
+other = "दलाव के अभिलेख"
+
[seealso_heading]
other = "यह भी देखें"
From 81ab20986ed93eb45a8ee735361d74af6d60ae4e Mon Sep 17 00:00:00 2001
From: NitishKumar06
Date: Wed, 5 Apr 2023 14:21:42 +0530
Subject: [PATCH 004/446] changes applied
---
data/i18n/hi/hi.toml | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/data/i18n/hi/hi.toml b/data/i18n/hi/hi.toml
index a8ec25549d..48397cc34a 100644
--- a/data/i18n/hi/hi.toml
+++ b/data/i18n/hi/hi.toml
@@ -9,7 +9,7 @@
other = "और"
[caution]
-other = "सावधानी:"
+other = "सावधान:"
[cleanup_heading]
other = "सफाई करना"
@@ -249,8 +249,6 @@ other = "2006-01-02"
# Deprecated. Planned for removal in a future release.
# Use [release_full_details_initial_text] instead.
-[release_complete]
-other = "पूर्ण"
# Replace [release_complete] with [release_full_details_initial_text]
[release_full_details_initial_text]
@@ -260,7 +258,7 @@ other = "पूर्ण"
other = "अनुसूची"
[release_changelog]
-other = "दलाव के अभिलेख"
+other = "बदलाव के अभिलेख"
[seealso_heading]
other = "यह भी देखें"
From 0501cfa489fc666802fb2c5e052363b524773cc4 Mon Sep 17 00:00:00 2001
From: Brandon High
Date: Tue, 18 Apr 2023 15:27:49 -0700
Subject: [PATCH 005/446] docs: Update kustomize examples to use non-deprecated
resources key (id lang)
---
.../docs/tasks/manage-kubernetes-objects/kustomization.md | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/content/id/docs/tasks/manage-kubernetes-objects/kustomization.md b/content/id/docs/tasks/manage-kubernetes-objects/kustomization.md
index 7cca240991..31a60ba26a 100644
--- a/content/id/docs/tasks/manage-kubernetes-objects/kustomization.md
+++ b/content/id/docs/tasks/manage-kubernetes-objects/kustomization.md
@@ -118,7 +118,7 @@ metadata:
#### secretGenerator
Kamu dapat membangkitkan Secret dari berkas atau pasangan _key-value_ literal. Untuk membangkitkan dari berkas, tambahkan entri pada daftar `files` di `secretGenerator`.
-Contoh di bawah ini membangkitkan Secret dengan data dari berkas:
+Contoh di bawah ini membangkitkan Secret dengan data dari berkas:
```shell
# Membuat berkas password.txt
@@ -719,14 +719,14 @@ _field_ lainnya yang bersinggungan di dalam **overlay** berbeda. Di bawah ini me
```shell
mkdir dev
cat < dev/kustomization.yaml
-bases:
+resources:
- ../base
namePrefix: dev-
EOF
mkdir prod
cat < prod/kustomization.yaml
-bases:
+resources:
- ../base
namePrefix: prod-
EOF
@@ -837,5 +837,3 @@ deployment.apps "dev-my-nginx" deleted
* [Buku Kubectl](https://kubectl.docs.kubernetes.io)
* [Rujukan Perintah Kubectl](/docs/reference/generated/kubectl/kubectl-commands/)
* [Rujukan API Kubernetes](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)
-
-
From d2d1242815ab093a756bdb87cffbdc2998d78d48 Mon Sep 17 00:00:00 2001
From: "m.nabokikh"
Date: Thu, 4 May 2023 11:15:45 +0200
Subject: [PATCH 006/446] KEP-3325: Promote SelfSubjectReview to GA
Signed-off-by: m.nabokikh
---
.../access-authn-authz/authentication.md | 16 ++++++++--------
.../feature-gates.md | 5 +++--
2 files changed, 11 insertions(+), 10 deletions(-)
diff --git a/content/en/docs/reference/access-authn-authz/authentication.md b/content/en/docs/reference/access-authn-authz/authentication.md
index ed0c8ef5cf..2ee21013c3 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.27" state="beta" >}}
+{{< feature-state for_k8s_version="v1.28" state="stable" >}}
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/v1beta1/selfsubjectreviews
+POST /apis/authentication.k8s.io/v1/selfsubjectreviews
```
```json
{
- "apiVersion": "authentication.k8s.io/v1beta1",
+ "apiVersion": "authentication.k8s.io/v1",
"kind": "SelfSubjectReview"
}
```
@@ -1243,7 +1243,7 @@ Response example:
```json
{
- "apiVersion": "authentication.k8s.io/v1beta1",
+ "apiVersion": "authentication.k8s.io/v1",
"kind": "SelfSubjectReview",
"status": {
"userInfo": {
@@ -1286,7 +1286,7 @@ By providing the output flag, it is also possible to print the JSON or YAML repr
{{% tab name="JSON" %}}
```json
{
- "apiVersion": "authentication.k8s.io/v1alpha1",
+ "apiVersion": "authentication.k8s.io/v1",
"kind": "SelfSubjectReview",
"status": {
"userInfo": {
@@ -1315,7 +1315,7 @@ By providing the output flag, it is also possible to print the JSON or YAML repr
{{% tab name="YAML" %}}
```yaml
-apiVersion: authentication.k8s.io/v1alpha1
+apiVersion: authentication.k8s.io/v1
kind: SelfSubjectReview
status:
userInfo:
@@ -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 (enabled by default after reaching Beta)
-* the API server for your cluster has the `authentication.k8s.io/v1alpha1` or `authentication.k8s.io/v1beta1`
+ is enabled for your cluster (enabled by default after reaching Beta and will be removed in Kubernetes v1.30)
+* the API server for your cluster has the `authentication.k8s.io/v1alpha1`, `authentication.k8s.io/v1beta1`, or `authentication.k8s.io/v1`
{{< 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 8441f0bc18..02a873d0ad 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
@@ -63,8 +63,6 @@ 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 | 1.26 |
-| `APISelfSubjectReview` | `true` | Beta | 1.27 | |
| `APIServerIdentity` | `false` | Alpha | 1.20 | 1.25 |
| `APIServerIdentity` | `true` | Beta | 1.26 | |
| `APIServerTracing` | `false` | Alpha | 1.22 | 1.26 |
@@ -228,6 +226,9 @@ For a reference to old feature gates that are removed, please refer to
| `AdvancedAuditing` | `false` | Alpha | 1.7 | 1.7 |
| `AdvancedAuditing` | `true` | Beta | 1.8 | 1.11 |
| `AdvancedAuditing` | `true` | GA | 1.12 | - |
+| `APISelfSubjectReview` | `false` | Alpha | 1.26 | 1.26 |
+| `APISelfSubjectReview` | `true` | Beta | 1.27 | 1.27 |
+| `APISelfSubjectReview` | `true` | GA | 1.28 | - |
| `CPUManager` | `false` | Alpha | 1.8 | 1.9 |
| `CPUManager` | `true` | Beta | 1.10 | 1.25 |
| `CPUManager` | `true` | GA | 1.26 | - |
From 30841950a6e4204d4fb18809a1b4177dcf198fe9 Mon Sep 17 00:00:00 2001
From: Maksim Nabokikh
Date: Thu, 4 May 2023 22:25:45 +0200
Subject: [PATCH 007/446] Apply suggestions from code review
Co-authored-by: Tim Bannister
---
.../en/docs/reference/access-authn-authz/authentication.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/content/en/docs/reference/access-authn-authz/authentication.md b/content/en/docs/reference/access-authn-authz/authentication.md
index 2ee21013c3..c3bbed6f88 100644
--- a/content/en/docs/reference/access-authn-authz/authentication.md
+++ b/content/en/docs/reference/access-authn-authz/authentication.md
@@ -1352,8 +1352,10 @@ 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 (enabled by default after reaching Beta and will be removed in Kubernetes v1.30)
-* the API server for your cluster has the `authentication.k8s.io/v1alpha1`, `authentication.k8s.io/v1beta1`, or `authentication.k8s.io/v1`
+ is enabled for your cluster (not needed for Kubernetes {{< skew currentVersion >}}, but older
+ Kubernetes versions might not offer this feature gate, or might default it to be off)
+* (if you are running a version of Kubernetes older than v1.28) 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 >}}
From c75d30872ae489cbb353593e9fd44b9c6bf5858e Mon Sep 17 00:00:00 2001
From: carlory
Date: Mon, 8 May 2023 17:39:23 +0800
Subject: [PATCH 008/446] move DelegateFSGroupToCSIDriver featuregate
---
.../command-line-tools-reference/feature-gates-removed.md | 7 +++++++
.../command-line-tools-reference/feature-gates.md | 6 ------
2 files changed, 7 insertions(+), 6 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 50d1dd29bf..734acc74db 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
@@ -117,6 +117,9 @@ In the following table:
| `DefaultPodTopologySpread` | `false` | Alpha | 1.19 | 1.19 |
| `DefaultPodTopologySpread` | `true` | Beta | 1.20 | 1.23 |
| `DefaultPodTopologySpread` | `true` | GA | 1.24 | 1.25 |
+| `DelegateFSGroupToCSIDriver` | `false` | Alpha | 1.22 | 1.22 |
+| `DelegateFSGroupToCSIDriver` | `true` | Beta | 1.23 | 1.25 |
+| `DelegateFSGroupToCSIDriver` | `true` | GA | 1.26 | 1.27 |
| `DynamicAuditing` | `false` | Alpha | 1.13 | 1.18 |
| `DynamicAuditing` | - | Deprecated | 1.19 | 1.19 |
| `DynamicKubeletConfig` | `false` | Alpha | 1.4 | 1.10 |
@@ -511,6 +514,10 @@ In the following table:
- `DefaultPodTopologySpread`: Enables the use of `PodTopologySpread` scheduling plugin to do
[default spreading](/docs/concepts/scheduling-eviction/topology-spread-constraints/#internal-default-constraints).
+- `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.
+
- `DynamicAuditing`: Used to enable dynamic auditing before v1.19.
- `DynamicKubeletConfig`: Enable the dynamic configuration of kubelet. 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 02a873d0ad..388bb46b41 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
@@ -268,9 +268,6 @@ For a reference to old feature gates that are removed, please refer to
| `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 |-|
| `DevicePlugins` | `false` | Alpha | 1.8 | 1.9 |
| `DevicePlugins` | `true` | Beta | 1.10 | 1.25 |
| `DevicePlugins` | `true` | GA | 1.26 | - |
@@ -509,9 +506,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `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.
- `DevicePlugins`: Enable the [device-plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
based resource provisioning on nodes.
- `DisableAcceleratorUsageMetrics`:
From b3c81f249c72a47327cf691d2fe93c3a6a5bfc21 Mon Sep 17 00:00:00 2001
From: able8
Date: Tue, 9 May 2023 22:19:16 +0800
Subject: [PATCH 009/446] Add go-template to kubectl output format
---
content/en/docs/reference/kubectl/cheatsheet.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content/en/docs/reference/kubectl/cheatsheet.md b/content/en/docs/reference/kubectl/cheatsheet.md
index 4f315c5e58..45699f2ce3 100644
--- a/content/en/docs/reference/kubectl/cheatsheet.md
+++ b/content/en/docs/reference/kubectl/cheatsheet.md
@@ -430,6 +430,8 @@ Output format | Description
--------------| -----------
`-o=custom-columns=` | Print a table using a comma separated list of custom columns
`-o=custom-columns-file=` | Print a table using the custom columns template in the `` file
+`-o=go-template=` | Print the fields defined in a [golang template](https://pkg.go.dev/text/template)
+`-o=go-template-file=` | Print the fields defined by the [golang template](https://pkg.go.dev/text/template) in the `` file
`-o=json` | Output a JSON formatted API object
`-o=jsonpath=` | Print the fields defined in a [jsonpath](/docs/reference/kubectl/jsonpath) expression
`-o=jsonpath-file=` | Print the fields defined by the [jsonpath](/docs/reference/kubectl/jsonpath) expression in the `` file
From 77e403d64352aaf4ef52dcc3ead1e921ba07e3a8 Mon Sep 17 00:00:00 2001
From: "Lubomir I. Ivanov"
Date: Mon, 15 May 2023 15:23:04 +0300
Subject: [PATCH 010/446] kubeadm: add the "config validate" command
Include the command in kubeadm-config.md.
The generated file is a placeholder and will be updated
before 1.28 releases.
---
.../generated/kubeadm_config_validate.md | 77 +++++++++++++++++++
.../setup-tools/kubeadm/kubeadm-config.md | 6 ++
2 files changed, 83 insertions(+)
create mode 100644 content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_validate.md
diff --git a/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_validate.md b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_validate.md
new file mode 100644
index 0000000000..c96ae18fb0
--- /dev/null
+++ b/content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_validate.md
@@ -0,0 +1,77 @@
+
+
+PLACEHOLDER
+
+### Synopsis
+
+PLACEHOLDER
+
+```
+kubeadm config validate [flags]
+```
+
+### Options
+
+
The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.
+
+
+
+
--rootfs string
+
+
+
[EXPERIMENTAL] The path to the 'real' host root filesystem.
+
+
+
+
+
+
+
diff --git a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-config.md b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-config.md
index b9908744e0..e21f6a00fd 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-config.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-config.md
@@ -31,6 +31,8 @@ For more information on using the kubeadm configuration API navigate to
You can use `kubeadm config migrate` to convert your old configuration files that contain a deprecated
API version to a newer, supported API version.
+`kubeadm config validate` can be used for validating a configuration file.
+
`kubeadm config images list` and `kubeadm config images pull` can be used to list and pull the images
that kubeadm requires.
@@ -51,6 +53,10 @@ that kubeadm requires.
{{< include "generated/kubeadm_config_migrate.md" >}}
+## kubeadm config validate {#cmd-config-validate}
+
+{{< include "generated/kubeadm_config_validate.md" >}}
+
## kubeadm config images list {#cmd-config-images-list}
{{< include "generated/kubeadm_config_images_list.md" >}}
From e7bc5e16af609d14f6092c372cdf919b2af808df Mon Sep 17 00:00:00 2001
From: Rishit Dagli
Date: Tue, 16 May 2023 13:47:55 -0400
Subject: [PATCH 011/446] Update hugo.toml for 1.28
---
hugo.toml | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/hugo.toml b/hugo.toml
index 43503425e2..7690dd887c 100644
--- a/hugo.toml
+++ b/hugo.toml
@@ -138,12 +138,12 @@ time_format_default = "January 02, 2006 at 3:04 PM PST"
description = "Production-Grade Container Orchestration"
showedit = true
-latest = "v1.27"
+latest = "v1.28"
-fullversion = "v1.27.0" # legacy; use {{< skew currentPatchVersion >}} instead
+fullversion = "v1.28.0" # legacy; use {{< skew currentPatchVersion >}} instead
# retain until all localizations have migrated
-version = "v1.27"
+version = "v1.28"
githubbranch = "main"
docsbranch = "main"
deprecated = false
@@ -182,13 +182,21 @@ js = [
"script"
]
+[[params.versions]]
+fullversion = "v1.28.0" # legacy; use {{< skew currentPatchVersion >}} instead
+ # retain until all localizations have migrated
+version = "v1.28"
+githubbranch = "v1.28.0"
+docsbranch = "main"
+url = "https://kubernetes.io"
+
[[params.versions]]
fullversion = "v1.27.0" # legacy; use {{< skew currentPatchVersion >}} instead
# retain until all localizations have migrated
version = "v1.27"
githubbranch = "v1.27.0"
-docsbranch = "main"
-url = "https://kubernetes.io"
+docsbranch = "release-1.27"
+url = "https://v1-27.docs.kubernetes.io"
[[params.versions]]
fullversion = "v1.26.3" # legacy; use {{< skew currentPatchVersion >}} instead
From f0eebb17b7681d7f22adfeab1d1495eeb5c3e4d1 Mon Sep 17 00:00:00 2001
From: carlory
Date: Fri, 12 May 2023 14:09:38 +0800
Subject: [PATCH 012/446] remove featuregate DevicePlugins
---
.../feature-gates-removed.md | 6 ++++++
.../command-line-tools-reference/feature-gates.md | 11 -----------
2 files changed, 6 insertions(+), 11 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 07931b0ed0..7daba03deb 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
@@ -137,6 +137,9 @@ In the following table:
| `DelegateFSGroupToCSIDriver` | `false` | Alpha | 1.22 | 1.22 |
| `DelegateFSGroupToCSIDriver` | `true` | Beta | 1.23 | 1.25 |
| `DelegateFSGroupToCSIDriver` | `true` | GA | 1.26 | 1.27 |
+| `DevicePlugins` | `false` | Alpha | 1.8 | 1.9 |
+| `DevicePlugins` | `true` | Beta | 1.10 | 1.25 |
+| `DevicePlugins` | `true` | GA | 1.26 | 1.27 |
| `DynamicAuditing` | `false` | Alpha | 1.13 | 1.18 |
| `DynamicAuditing` | - | Deprecated | 1.19 | 1.19 |
| `DynamicKubeletConfig` | `false` | Alpha | 1.4 | 1.10 |
@@ -571,6 +574,9 @@ In the following table:
role of applying `fsGroup` from a Pod's `securityContext` to the driver by
passing `fsGroup` through the NodeStageVolume and NodePublishVolume CSI calls.
+- `DevicePlugins`: Enable the [device-plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
+ based resource provisioning on nodes.
+
- `DynamicAuditing`: Used to enable dynamic auditing before v1.19.
- `DynamicKubeletConfig`: Enable the dynamic configuration of kubelet. 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 0d874ee3de..ba21bf029c 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
@@ -259,12 +259,6 @@ For a reference to old feature gates that are removed, please refer to
| `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 |-|
-| `DevicePlugins` | `false` | Alpha | 1.8 | 1.9 |
-| `DevicePlugins` | `true` | Beta | 1.10 | 1.25 |
-| `DevicePlugins` | `true` | GA | 1.26 | - |
| `DisableAcceleratorUsageMetrics` | `false` | Alpha | 1.19 | 1.19 |
| `DisableAcceleratorUsageMetrics` | `true` | Beta | 1.20 | 1.24 |
| `DisableAcceleratorUsageMetrics` | `true` | GA | 1.25 |- |
@@ -472,11 +466,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `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.
-- `DevicePlugins`: Enable the [device-plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
- based resource provisioning on nodes.
- `DisableAcceleratorUsageMetrics`:
[Disable accelerator metrics collected by the kubelet](/docs/concepts/cluster-administration/system-metrics/#disable-accelerator-metrics).
- `DisableCloudProviders`: Disables any functionality in `kube-apiserver`,
From 970317e25df7bdd4378142dbc0b1cb4994cb8502 Mon Sep 17 00:00:00 2001
From: Rishit Dagli
Date: Wed, 17 May 2023 15:13:33 -0400
Subject: [PATCH 013/446] Remove 1.23 from versions dropdown
---
hugo.toml | 8 --------
1 file changed, 8 deletions(-)
diff --git a/hugo.toml b/hugo.toml
index 7690dd887c..87fe123737 100644
--- a/hugo.toml
+++ b/hugo.toml
@@ -222,14 +222,6 @@ githubbranch = "v1.24.12"
docsbranch = "release-1.24"
url = "https://v1-24.docs.kubernetes.io"
-[[params.versions]]
-fullversion = "v1.23.17" # legacy; use {{< skew currentPatchVersion >}} instead
- # retain until all localizations have migrated
-version = "v1.23"
-githubbranch = "v1.23.17"
-docsbranch = "release-1.23"
-url = "https://v1-23.docs.kubernetes.io"
-
# User interface configuration
[params.ui]
# Enable to show the side bar menu in its compact state.
From 02f092e65ec3305eb38301776edb6e602c6e9fdc Mon Sep 17 00:00:00 2001
From: 9bany
Date: Thu, 11 May 2023 16:32:12 +0700
Subject: [PATCH 014/446] [En] replace all references to
https://storage.googleapis.com/kubernetes-release to https://dl.k8s.ioadd log
---
.../_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md | 2 +-
...9-03-28-running-kubernetes-locally-on-linux-with-minikube.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md b/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md
index 5625b21fc3..b5b8b82429 100644
--- a/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md
+++ b/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md
@@ -85,7 +85,7 @@ f017f405ff4b gcr.io/google\_containers/hyperkube-arm:v1.1.2 "/hyperkube
When that’s looking good we’re able to access the master node of the Kubernetes cluster with kubectl. Kubectl for ARM can be downloaded from googleapis storage. kubectl get nodes shows which cluster nodes are registered with its status. The master node is named 127.0.0.1.
```
-$ curl -fsSL -o /usr/bin/kubectl https://storage.googleapis.com/kubernetes-release/release/v1.1.2/bin/linux/arm/kubectl
+$ curl -fsSL -o /usr/bin/kubectl https://dl.k8s.io/release/v1.1.2/bin/linux/arm/kubectl
$ kubectl get nodes
diff --git a/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md b/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
index ebbf591772..1d9a43351c 100644
--- a/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
+++ b/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
@@ -80,7 +80,7 @@ In order to manage the Kubernetes cluster, we need to install [kubectl](https://
The recommended way to install it on Linux is to download the pre-built binary and move it to a directory under the `$PATH`.
```shell
-curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl \
+curl -LO https://dl.k8s.io/release/$(curl -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl \
&& sudo install kubectl /usr/local/bin && rm kubectl
```
From 5c4d0a56ac5b12fb934f91c4cc1308a29cf553b1 Mon Sep 17 00:00:00 2001
From: bany <53461381+9bany@users.noreply.github.com>
Date: Tue, 23 May 2023 23:38:15 +0700
Subject: [PATCH 015/446] add -L
Co-authored-by: Tim Bannister
---
...9-03-28-running-kubernetes-locally-on-linux-with-minikube.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md b/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
index 1d9a43351c..097da0e1d2 100644
--- a/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
+++ b/content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md
@@ -80,7 +80,7 @@ In order to manage the Kubernetes cluster, we need to install [kubectl](https://
The recommended way to install it on Linux is to download the pre-built binary and move it to a directory under the `$PATH`.
```shell
-curl -LO https://dl.k8s.io/release/$(curl -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl \
+curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl \
&& sudo install kubectl /usr/local/bin && rm kubectl
```
From edb80667ce5516ff83743eac4450ef5c84849c40 Mon Sep 17 00:00:00 2001
From: bany <53461381+9bany@users.noreply.github.com>
Date: Tue, 23 May 2023 23:38:49 +0700
Subject: [PATCH 016/446] add -L
Co-authored-by: Tim Bannister
---
.../_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md b/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md
index b5b8b82429..25ecb8485d 100644
--- a/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md
+++ b/content/en/blog/_posts/2015-12-00-Creating-Raspberry-Pi-Cluster-Running.md
@@ -85,7 +85,7 @@ f017f405ff4b gcr.io/google\_containers/hyperkube-arm:v1.1.2 "/hyperkube
When that’s looking good we’re able to access the master node of the Kubernetes cluster with kubectl. Kubectl for ARM can be downloaded from googleapis storage. kubectl get nodes shows which cluster nodes are registered with its status. The master node is named 127.0.0.1.
```
-$ curl -fsSL -o /usr/bin/kubectl https://dl.k8s.io/release/v1.1.2/bin/linux/arm/kubectl
+$ curl -fsSL -L -o /usr/bin/kubectl https://dl.k8s.io/release/v1.1.2/bin/linux/arm/kubectl
$ kubectl get nodes
From 5c29d1dd6bd920a5fbc931b229b9b0c86e0584df Mon Sep 17 00:00:00 2001
From: Dipesh Rawat
Date: Mon, 29 May 2023 17:57:24 +0100
Subject: [PATCH 017/446] Add layout to hide outdated releases
---
content/en/releases/_index.md | 1 +
data/i18n/en/en.toml | 2 +-
layouts/docs/release-info.html | 5 +++++
3 files changed, 7 insertions(+), 1 deletion(-)
create mode 100644 layouts/docs/release-info.html
diff --git a/content/en/releases/_index.md b/content/en/releases/_index.md
index 5b62f95d82..2dab2391d5 100644
--- a/content/en/releases/_index.md
+++ b/content/en/releases/_index.md
@@ -2,6 +2,7 @@
linktitle: Release History
title: Releases
type: docs
+layout: release-info
---
diff --git a/data/i18n/en/en.toml b/data/i18n/en/en.toml
index 149e0204a1..a31ac63dca 100644
--- a/data/i18n/en/en.toml
+++ b/data/i18n/en/en.toml
@@ -65,7 +65,7 @@ other = "(last updated: %s)"
other = "You are viewing documentation for Kubernetes version:"
[deprecation_warning]
-other = " documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the "
+other = " documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date information, see the "
[deprecation_file_warning]
other = "Deprecated"
diff --git a/layouts/docs/release-info.html b/layouts/docs/release-info.html
new file mode 100644
index 0000000000..d5e61ee88b
--- /dev/null
+++ b/layouts/docs/release-info.html
@@ -0,0 +1,5 @@
+{{ define "main" }}
+{{ if not .Site.Params.deprecated }}
+ {{ .Content }}
+{{ end }}
+{{ end }}
\ No newline at end of file
From 8d42b3a9a09af947e16f04d318d07231dc4d1e8e Mon Sep 17 00:00:00 2001
From: Gunju Kim
Date: Wed, 12 Apr 2023 22:38:02 +0900
Subject: [PATCH 018/446] Update ExpandedDNSConfig docs for GA
---
.../en/docs/concepts/services-networking/dns-pod-service.md | 2 +-
.../reference/command-line-tools-reference/feature-gates.md | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/concepts/services-networking/dns-pod-service.md b/content/en/docs/concepts/services-networking/dns-pod-service.md
index d5cb855626..731e593628 100644
--- a/content/en/docs/concepts/services-networking/dns-pod-service.md
+++ b/content/en/docs/concepts/services-networking/dns-pod-service.md
@@ -292,7 +292,7 @@ Below are the properties a user can specify in the `dnsConfig` field:
This property is optional. When specified, the provided list will be merged
into the base search domain names generated from the chosen DNS policy.
Duplicate domain names are removed.
- Kubernetes allows for at most 6 search domains.
+ Kubernetes allows up to 32 search domains.
- `options`: an optional list of objects where each object may have a `name`
property (required) and a `value` property (optional). The contents in this
property will be merged to the options generated from the specified DNS policy.
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 ba21bf029c..697cba935a 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
@@ -99,8 +99,6 @@ For a reference to old feature gates that are removed, please refer to
| `ElasticIndexedJob` | `true` | Beta` | 1.27 | |
| `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 | |
| `GracefulNodeShutdown` | `false` | Alpha | 1.20 | 1.20 |
| `GracefulNodeShutdown` | `true` | Beta | 1.21 | |
@@ -276,6 +274,9 @@ For a reference to old feature gates that are removed, please refer to
| `EndpointSliceTerminatingCondition` | `true` | Beta | 1.22 | 1.25 |
| `EndpointSliceTerminatingCondition` | `true` | GA | 1.26 | |
| `ExecProbeTimeout` | `true` | GA | 1.20 | - |
+| `ExpandedDNSConfig` | `false` | Alpha | 1.22 | 1.25 |
+| `ExpandedDNSConfig` | `true` | Beta | 1.26 | 1.27 |
+| `ExpandedDNSConfig` | `true` | GA | 1.28 | - |
| `GRPCContainerProbe` | `false` | Alpha | 1.23 | 1.23 |
| `GRPCContainerProbe` | `true` | Beta | 1.24 | 1.26 |
| `GRPCContainerProbe` | `true` | GA | 1.27 | |
From 485133f805812c0b31740176e0eeb98d0005ef40 Mon Sep 17 00:00:00 2001
From: xuzhenglun
Date: Tue, 9 May 2023 13:47:31 +0800
Subject: [PATCH 019/446] promote ServiceNodePortStaticSubrange to beta
---
content/en/docs/concepts/services-networking/service.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/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md
index 85cf6285a8..52f794cb0e 100644
--- a/content/en/docs/concepts/services-networking/service.md
+++ b/content/en/docs/concepts/services-networking/service.md
@@ -516,7 +516,7 @@ spec:
#### Reserve Nodeport Ranges to avoid collisions when port assigning
-{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.28" state="beta" >}}
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
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 ba21bf029c..fa779a27df 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
@@ -195,7 +195,8 @@ For a reference to old feature gates that are removed, please refer to
| `SELinuxMountReadWriteOncePod` | `false` | Alpha | 1.25 | 1.26 |
| `SELinuxMountReadWriteOncePod` | `true` | Beta | 1.27 | |
| `SecurityContextDeny` | `false` | Alpha | 1.27 | |
-| `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | |
+| `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | 1.27 |
+| `ServiceNodePortStaticSubrange` | `true` | Beta | 1.28 | |
| `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
| `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
| `StableLoadBalancerNodeGet` | `true` | Beta | 1.27 | |
From f5cd33255260fd0b060c79247917e2d302f09cb2 Mon Sep 17 00:00:00 2001
From: tinatingyu
Date: Fri, 26 May 2023 17:06:58 +0000
Subject: [PATCH 020/446] Add LegacyServiceAccountTokenCleanUp feature in alpha
and Update LegacyServiceAccountTokenTracking to GA.
---
.../command-line-tools-reference/feature-gates.md | 13 +++++++++----
1 file changed, 9 insertions(+), 4 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 ba21bf029c..90b4fef40c 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
@@ -136,8 +136,7 @@ For a reference to old feature gates that are removed, please refer to
| `KubeletPodResourcesGetAllocatable` | `true` | Beta | 1.23 | |
| `KubeletTracing` | `false` | Alpha | 1.25 | 1.26 |
| `KubeletTracing` | `true` | Beta | 1.27 | |
-| `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
-| `LegacyServiceAccountTokenTracking` | `true` | Beta | 1.27 | |
+| `LegacyServiceAccountTokenCleanUp` | `false` | Alpha | 1.28 | |
| `LocalStorageCapacityIsolationFSQuotaMonitoring` | `false` | Alpha | 1.15 | - |
| `LogarithmicScaleDown` | `false` | Alpha | 1.21 | 1.21 |
| `LogarithmicScaleDown` | `true` | Beta | 1.22 | |
@@ -290,6 +289,9 @@ 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 | - |
+| `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
+| `LegacyServiceAccountTokenTracking` | `true` | Beta | 1.27 | 1.27 |
+| `LegacyServiceAccountTokenTracking` | `true` | GA | 1.28 | - |
| `MixedProtocolLBService` | `false` | Alpha | 1.20 | 1.23 |
| `MixedProtocolLBService` | `true` | Beta | 1.24 | 1.25 |
| `MixedProtocolLBService` | `true` | GA | 1.26 | - |
@@ -580,9 +582,12 @@ Each feature gate is designed for enabling/disabling a specific feature:
OpenTelemetry trace spans.
See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/system-traces) for more details.
- `LegacyServiceAccountTokenNoAutoGeneration`: Stop auto-generation of Secret-based
- [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens).
+ [service account tokens](/docs/concepts/security/service-accounts/#get-a-token).
+- `LegacyServiceAccountTokenCleanUp`: Enable cleaning up Secret-based
+ [service account tokens](/docs/concepts/security/service-accounts/#get-a-token)
+ when they are not used in a specified time (default to be one year).
- `LegacyServiceAccountTokenTracking`: Track usage of Secret-based
- [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens).
+ [service account tokens](/docs/concepts/security/service-accounts/#get-a-token).
- `LocalStorageCapacityIsolationFSQuotaMonitoring`: When `LocalStorageCapacityIsolation`
is enabled for
[local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/)
From 6f9fec35ac0d3d57d1c401caaa0f3e921b171542 Mon Sep 17 00:00:00 2001
From: carlory
Date: Tue, 6 Jun 2023 18:28:52 +0800
Subject: [PATCH 021/446] node: graduate the podresources API endpoint to GA
---
.../reference/command-line-tools-reference/feature-gates.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index ec40607a63..441a703a74 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,8 +126,6 @@ For a reference to old feature gates that are removed, please refer to
| `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 |
@@ -289,6 +287,9 @@ For a reference to old feature gates that are removed, please refer to
| `KubeletCredentialProviders` | `false` | Alpha | 1.20 | 1.23 |
| `KubeletCredentialProviders` | `true` | Beta | 1.24 | 1.25 |
| `KubeletCredentialProviders` | `true` | GA | 1.26 | - |
+| `KubeletPodResources` | `false` | Alpha | 1.13 | 1.14 |
+| `KubeletPodResources` | `true` | Beta | 1.15 | 1.27 |
+| `KubeletPodResources` | `true` | GA | 1.28 | - |
| `LegacyServiceAccountTokenNoAutoGeneration` | `true` | Beta | 1.24 | 1.25 |
| `LegacyServiceAccountTokenNoAutoGeneration` | `true` | GA | 1.26 | - |
| `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
From 290b12ca94678de56da770662a73a15f89478b08 Mon Sep 17 00:00:00 2001
From: Vaibhav Goel <79974025+vaibhav2107@users.noreply.github.com>
Date: Tue, 13 Jun 2023 06:29:57 +0530
Subject: [PATCH 022/446] Removed the keyword new from
dynamic-resource-allocation.md (#41483)
* Removed the new keyword from dynamic-resource-allocation.md
* Updated the grammar in dynamic-resource-allocation.md
---
.../scheduling-eviction/dynamic-resource-allocation.md | 6 +++---
1 file changed, 3 insertions(+), 3 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 cd7f5a0373..f08eb3cf53 100644
--- a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
+++ b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@@ -11,7 +11,7 @@ weight: 65
{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
-Dynamic resource allocation is a new API for requesting and sharing resources
+Dynamic resource allocation is an API for requesting and sharing resources
between pods and containers inside a pod. It is a generalization of the
persistent volumes API for generic resources. Third-party resource drivers are
responsible for tracking and allocating resources. Different kinds of
@@ -32,7 +32,7 @@ check the documentation for that version of Kubernetes.
## API
The `resource.k8s.io/v1alpha2` {{< glossary_tooltip text="API group"
-term_id="api-group" >}} provides four new types:
+term_id="api-group" >}} provides four types:
ResourceClass
: Defines which resource driver handles a certain kind of
@@ -61,7 +61,7 @@ typically using the type defined by a {{< glossary_tooltip
term_id="CustomResourceDefinition" text="CRD" >}} that was created when
installing a resource driver.
-The `core/v1` `PodSpec` defines ResourceClaims that are needed for a Pod in a new
+The `core/v1` `PodSpec` defines ResourceClaims that are needed for a Pod in a
`resourceClaims` field. Entries in that list reference either a ResourceClaim
or a ResourceClaimTemplate. When referencing a ResourceClaim, all Pods using
this PodSpec (for example, inside a Deployment or StatefulSet) share the same
From 544996eee2d0642e0fdd10f1f98b7f1fb0026d48 Mon Sep 17 00:00:00 2001
From: Dipesh Rawat
Date: Tue, 13 Jun 2023 21:14:32 +0100
Subject: [PATCH 023/446] Add dipesh to reviewers
---
OWNERS_ALIASES | 1 +
1 file changed, 1 insertion(+)
diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES
index 0fc49a21ce..701dce89b1 100644
--- a/OWNERS_ALIASES
+++ b/OWNERS_ALIASES
@@ -41,6 +41,7 @@ aliases:
- tengqm
sig-docs-en-reviews: # PR reviews for English content
- bradtopol
+ - dipesh-rawat
- divya-mohan0209
- kbhawkey
- mehabhalodiya
From 01c9decf7d85d0630f843b2a4c96322a270e50ad Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Fri, 16 Jun 2023 16:44:19 -0700
Subject: [PATCH 024/446] rename PodHasNetwork to PodReadyToStartContainers
(#40945)
* rename PodHasNetwork to PodReadyToStartContainers
* add note for condition rename
* add feature gate removal
* Update content/en/docs/reference/command-line-tools-reference/feature-gates.md
Co-authored-by: Qiming Teng
* Update content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
Co-authored-by: Qiming Teng
* Update content/en/docs/reference/command-line-tools-reference/feature-gates-removed.md
Co-authored-by: Qiming Teng
---------
Co-authored-by: Qiming Teng
---
.../concepts/workloads/pods/pod-lifecycle.md | 16 ++++++++++------
.../feature-gates-removed.md | 3 +++
.../feature-gates.md | 5 +++--
3 files changed, 16 insertions(+), 8 deletions(-)
diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
index b209a6a65f..ff7090ac5c 100644
--- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -164,7 +164,7 @@ through which the Pod has or has not passed. Kubelet manages the following
PodConditions:
* `PodScheduled`: the Pod has been scheduled to a node.
-* `PodHasNetwork`: (alpha feature; must be [enabled explicitly](#pod-has-network)) the
+* `PodReadyToStartContainers`: (alpha feature; must be [enabled explicitly](#pod-has-network)) the
Pod sandbox has been successfully created and networking configured.
* `ContainersReady`: all containers in the Pod are ready.
* `Initialized`: all [init containers](/docs/concepts/workloads/pods/init-containers/)
@@ -244,15 +244,19 @@ When a Pod's containers are Ready but at least one custom condition is missing o
{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
+{{< note >}}
+This condition was renamed from PodHasNetwork to PodReadyToStartContainers.
+{{< /note >}}
+
After a Pod gets scheduled on a node, it needs to be admitted by the Kubelet and
have any volumes mounted. Once these phases are complete, the Kubelet works with
a container runtime (using {{< glossary_tooltip term_id="cri" >}}) to set up a
runtime sandbox and configure networking for the Pod. If the
-`PodHasNetworkCondition` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled,
+`PodReadyToStartContainersCondition` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled,
Kubelet reports whether a pod has reached this initialization milestone through
-the `PodHasNetwork` condition in the `status.conditions` field of a Pod.
+the `PodReadyToStartContainers` condition in the `status.conditions` field of a Pod.
-The `PodHasNetwork` condition is set to `False` by the Kubelet when it detects a
+The `PodReadyToStartContainers` condition is set to `False` by the Kubelet when it detects a
Pod does not have a runtime sandbox with networking configured. This occurs in
the following scenarios:
* Early in the lifecycle of the Pod, when the kubelet has not yet begun to set up a sandbox for the Pod using the container runtime.
@@ -262,10 +266,10 @@ the following scenarios:
* for container runtimes that use virtual machines for isolation, the Pod
sandbox virtual machine rebooting, which then requires creating a new sandbox and fresh container network configuration.
-The `PodHasNetwork` condition is set to `True` by the kubelet after the
+The `PodReadyToStartContainers` condition is set to `True` by the kubelet after the
successful completion of sandbox creation and network configuration for the Pod
by the runtime plugin. The kubelet can start pulling container images and create
-containers after `PodHasNetwork` condition has been set to `True`.
+containers after `PodReadyToStartContainers` condition has been set to `True`.
For a Pod with init containers, the kubelet sets the `Initialized` condition to
`True` after the init containers have successfully completed (which happens
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 d896f89a3b..7cfad6315d 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
@@ -250,6 +250,7 @@ In the following table:
| `PodDisruptionBudget` | `false` | Alpha | 1.3 | 1.4 |
| `PodDisruptionBudget` | `true` | Beta | 1.5 | 1.20 |
| `PodDisruptionBudget` | `true` | GA | 1.21 | 1.25 |
+| `PodHasNetworkCondition` | `false` | Alpha | 1.25 | 1.27 |
| `PodOverhead` | `false` | Alpha | 1.16 | 1.17 |
| `PodOverhead` | `true` | Beta | 1.18 | 1.23 |
| `PodOverhead` | `true` | GA | 1.24 | 1.25 |
@@ -712,6 +713,8 @@ In the following table:
- `PodDisruptionBudget`: Enable the [PodDisruptionBudget](/docs/tasks/run-application/configure-pdb/) feature.
+- `PodHasNetwork`: Enable the kubelet to mark the [PodHasNetwork](/docs/concepts/workloads/pods/pod-lifecycle/#pod-has-network)
+ condition on pods. This was renamed to `PodReadyToStartContainersCondition` in 1.28.
- `PodOverhead`: Enable the [PodOverhead](/docs/concepts/scheduling-eviction/pod-overhead/)
feature to account for pod overheads.
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 ec40607a63..1061a15f5e 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
@@ -170,7 +170,7 @@ For a reference to old feature gates that are removed, please refer to
| `PodDeletionCost` | `true` | Beta | 1.22 | |
| `PodDisruptionConditions` | `false` | Alpha | 1.25 | 1.25 |
| `PodDisruptionConditions` | `true` | Beta | 1.26 | |
-| `PodHasNetworkCondition` | `false` | Alpha | 1.25 | |
+| `PodReadyToStartContainersCondition` | `false` | Alpha | 1.28 | |
| `PodSchedulingReadiness` | `false` | Alpha | 1.26 | 1.26 |
| `PodSchedulingReadiness` | `true` | Beta | 1.27 | |
| `ProbeTerminationGracePeriod` | `false` | Alpha | 1.21 | 1.21 |
@@ -653,7 +653,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `PodAndContainerStatsFromCRI`: Configure the kubelet to gather container and pod stats from the CRI container runtime rather than gathering them from cAdvisor.
As of 1.26, this also includes gathering metrics from CRI and emitting them over `/metrics/cadvisor` (rather than having cAdvisor emit them directly).
- `PodDisruptionConditions`: Enables support for appending a dedicated pod condition indicating that the pod is being deleted due to a disruption.
-- `PodHasNetworkCondition`: Enable the kubelet to mark the [PodHasNetwork](/docs/concepts/workloads/pods/pod-lifecycle/#pod-has-network) condition on pods.
+- `PodReadyToStartContainersCondition`: Enable the kubelet to mark the [PodReadyToStartContainers](/docs/concepts/workloads/pods/pod-lifecycle/#pod-has-network)
+ condition on pods. This was previously (1.25-1.27) known as `PodHasNetworkCondition`.
- `PodSchedulingReadiness`: Enable setting `schedulingGates` field to control a Pod's [scheduling readiness](/docs/concepts/scheduling-eviction/pod-scheduling-readiness).
- `PodSecurity`: Enables the `PodSecurity` admission plugin.
- `ProbeTerminationGracePeriod`: Enable [setting probe-level
From d5a2a693f38c1dcca9ad8d5b4d8614787e0229fa Mon Sep 17 00:00:00 2001
From: SataQiu
Date: Wed, 21 Jun 2023 13:33:53 +0800
Subject: [PATCH 025/446] kubeadm: add docs for UpgradeAddonsBeforeControlPlane
feature gate
---
.../setup-tools/kubeadm/kubeadm-init.md | 24 +++++++++++++++++++
.../kubeadm/kubeadm-upgrade.md | 14 +++++++++++
2 files changed, 38 insertions(+)
diff --git a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
index 4d102d1a15..bbc1f104ad 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
@@ -189,6 +189,30 @@ or `kubeadm upgrade apply`), kubeadm respects the value of `UnversionedKubeletCo
(during `kubeadm join`, `kubeadm reset`, `kubeadm upgrade ...`), kubeadm attempts to use unversioned ConfigMap name first;
if that does not succeed, kubeadm falls back to using the legacy (versioned) name for that ConfigMap.
+List of deprecated feature gates:
+
+{{< table caption="kubeadm deprecated feature gates" >}}
+Feature | Default
+:-------|:--------
+`UpgradeAddonsBeforeControlPlane` | `false`
+{{< /table >}}
+
+Feature gate descriptions:
+
+`UpgradeAddonsBeforeControlPlane`
+: This is as a **disabled** feature gate that was introduced for Kubernetes v1.28, in order to allow reactivating a legacy
+and deprecated behavior during cluster upgrade. For kubeadm versions prior to v1.28, kubeadm upgrades cluster addons (including
+CoreDNS and kube-proxy) immediately during `kubeadm upgrade apply`, regardless of whether there are other control plane
+instances that have not been upgraded. This may cause compatibility problems. Since v1.28, kubeadm defaults to a mode that
+always checks whether all the control plane instances have been upgraded before starting to upgrade the addons. This behavior
+is applied to both `kubeadm upgrade apply` and `kubeadm upgrade node`. kubeadm determines whether a control plane instance
+has been upgraded by checking whether the image of the kube-apiserver Pod has been upgraded. You must perform control plane
+instances upgrade sequentially or at least ensure that the last control plane instance upgrade is not started until all the
+other control plane instances have been upgraded completely, and the addons upgrade will be performed after the last control plane
+instance is upgraded. The deprecated `UpgradeAddonsBeforeControlPlane` feature gate gives you a chance to keep the old upgrade
+behavior. You should not need this old behavior; if you do, you should consider changing your cluster or upgrade processes, as this
+feature gate will be removed in a future release.
+
### Adding kube-proxy parameters {#kube-proxy}
For information about kube-proxy parameters in the kubeadm configuration see:
diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md
index 82bbecca05..9db7e3e7df 100644
--- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md
+++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md
@@ -152,6 +152,20 @@ Pick a control plane node that you wish to upgrade first. It must have the `/etc
[upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so.
```
+ {{< note >}}
+ For versions earlier than v1.28, kubeadm defaulted to a mode that upgrades the addons (including CoreDNS and kube-proxy)
+ immediately during `kubeadm upgrade apply`, regardless of whether there are other control plane instances that have not
+ been upgraded. This may cause compatibility problems. Since v1.28, kubeadm defaults to a mode that checks whether all
+ the control plane instances have been upgraded before starting to upgrade the addons. You must perform control plane
+ instances upgrade sequentially or at least ensure that the last control plane instance upgrade is not started until all
+ the other control plane instances have been upgraded completely, and the addons upgrade will be performed after the last
+ control plane instance is upgraded. If you want to keep the old upgrade behavior, please enable the `UpgradeAddonsBeforeControlPlane`
+ feature gate by `kubeadm upgrade apply --feature-gates=UpgradeAddonsBeforeControlPlane=true`. The Kubernetes project does
+ not in general recommend enabling this feature gate, you should instead change your upgrade process or cluster addons so
+ that you do not need to enable the legacy behavior. The `UpgradeAddonsBeforeControlPlane` feature gate will be removed in
+ a future release.
+ {{ note >}}
+
1. Manually upgrade your CNI provider plugin.
Your Container Network Interface (CNI) provider may have its own upgrade instructions to follow.
From 360170b1eaad503466d48c2487901642b6ce70fc Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Fri, 23 Jun 2023 09:35:42 -0400
Subject: [PATCH 026/446] rename PodHasNetwork to PodReadyToStartContainers as
part of alpha rename
---
.../2022-09-14-pod-has-network-condition.md | 36 +++++++++----------
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
index 00bd8ad977..fc34e1d6a4 100644
--- a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
+++ b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
@@ -1,6 +1,6 @@
---
layout: blog
-title: 'Kubernetes 1.25: PodHasNetwork Condition for Pods'
+title: 'Kubernetes 1.25: PodReadyToStart Condition for Pods'
date: 2022-09-14
slug: pod-has-network-condition
---
@@ -9,18 +9,18 @@ slug: pod-has-network-condition
Deep Debroy (Apple)
Kubernetes 1.25 introduces Alpha support for a new kubelet-managed pod condition
-in the status field of a pod: `PodHasNetwork`. The kubelet, for a worker node,
-will use the `PodHasNetwork` condition to accurately surface the initialization
+in the status field of a pod: `PodReadyToStartContainers`. The kubelet, for a worker node,
+will use the `PodReadyToStartContainers` condition to accurately surface the initialization
state of a pod from the perspective of pod sandbox creation and network
configuration by a container runtime (typically in coordination with CNI
plugins). The kubelet starts to pull container images and start individual
-containers (including init containers) after the status of the `PodHasNetwork`
+containers (including init containers) after the status of the `PodReadyToStartContainers`
condition is set to `"True"`. Metrics collection services that report latency of
pod initialization from a cluster infrastructural perspective (i.e. agnostic of
per container characteristics like image size or payload) can utilize the
-`PodHasNetwork` condition to accurately generate Service Level Indicators
+`PodReadyToStartContainers` condition to accurately generate Service Level Indicators
(SLIs). Certain operators or controllers that manage underlying pods may utilize
-the `PodHasNetwork` condition to optimize the set of actions performed when pods
+the `PodReadyToStartContainers` condition to optimize the set of actions performed when pods
repeatedly fail to come up.
### How is this different from the existing Initialized condition reported for pods?
@@ -44,14 +44,14 @@ containers will report the status of the `Initialized` condition as `"True"`
even if the container runtime is not able to successfully initialize the pod
sandbox environment.
-Relative to either situation above, the `PodHasNetwork` condition surfaces more
+Relative to either situation above, the `PodReadyToStartContainers` condition surfaces more
accurate data around when the pod runtime sandbox was initialized with
networking configured so that the kubelet can proceed to launch user-configured
containers (including init containers) in the pod.
### Special Cases
-If a pod specifies `hostNetwork` as `"True"`, the `PodHasNetwork` condition is
+If a pod specifies `hostNetwork` as `"True"`, the `PodReadyToStartContainers` condition is
set to `"True"` based on successful creation of the pod sandbox while the
network configuration state of the pod sandbox is ignored. This is because the
CRI implementation typically skips any pod sandbox network configuration when
@@ -61,17 +61,17 @@ A node agent may dynamically re-configure network interface(s) for a pod by
watching changes in pod annotations that specify additional networking
configuration (e.g. `k8s.v1.cni.cncf.io/networks`). Dynamic updates of pod
networking configuration after the pod sandbox is initialized by Kubelet (in
-coordination with a container runtime) are not reflected by the `PodHasNetwork`
+coordination with a container runtime) are not reflected by the `PodReadyToStartContainers`
condition.
-### Try out the PodHasNetwork condition for pods
+### Try out the PodReadyToStartContainers condition for pods
-In order to have the kubelet report the `PodHasNetwork` condition in the status
-field of a pod, please enable the `PodHasNetworkCondition` feature gate on the
+In order to have the kubelet report the `PodReadyToStartContainers` condition in the status
+field of a pod, please enable the `PodReadyToStartContainersCondition` feature gate on the
kubelet.
For a pod whose runtime sandbox has been successfully created and has networking
-configured, the kubelet will report the `PodHasNetwork` condition with status set to `"True"`:
+configured, the kubelet will report the `PodReadyToStartContainers` condition with status set to `"True"`:
```
$ kubectl describe pod nginx1
@@ -80,7 +80,7 @@ Namespace: default
...
Conditions:
Type Status
- PodHasNetwork True
+ PodReadyToStartContainers True
Initialized True
Ready True
ContainersReady True
@@ -88,7 +88,7 @@ Conditions:
```
For a pod whose runtime sandbox has not been created yet (and networking not
-configured either), the kubelet will report the `PodHasNetwork` condition with
+configured either), the kubelet will report the `PodReadyToStartContainers` condition with
status set to `"False"`:
```
@@ -98,7 +98,7 @@ Namespace: default
...
Conditions:
Type Status
- PodHasNetwork False
+ PodReadyToStartContainers False
Initialized True
Ready False
ContainersReady False
@@ -108,13 +108,13 @@ Conditions:
### What’s next?
Depending on feedback and adoption, the Kubernetes team plans to push the
-reporting of the `PodHasNetwork` condition to Beta in 1.26 or 1.27.
+reporting of the `PodReadyToStartContainers` condition to Beta in 1.26 or 1.27.
### How can I learn more?
Please check out the
[documentation](/docs/concepts/workloads/pods/pod-lifecycle/) for the
-`PodHasNetwork` condition to learn more about it and how it fits in relation to
+`PodReadyToStartContainers` condition to learn more about it and how it fits in relation to
other pod conditions.
### How to get involved?
From e0a9d6aed595cd4d314ec79127173b8407e5f76b Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Fri, 23 Jun 2023 09:43:58 -0400
Subject: [PATCH 027/446] update blog post with latest name
---
content/en/blog/_posts/2022-09-14-pod-has-network-condition.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
index fc34e1d6a4..f19b91e4f9 100644
--- a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
+++ b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
@@ -1,6 +1,6 @@
---
layout: blog
-title: 'Kubernetes 1.25: PodReadyToStart Condition for Pods'
+title: 'Kubernetes 1.25: PodReadyToStartContainers Condition for Pods'
date: 2022-09-14
slug: pod-has-network-condition
---
From 1732bd8fc0a08b128b8c69250c15a59d9242d4c5 Mon Sep 17 00:00:00 2001
From: Vilsol
Date: Sun, 25 Jun 2023 22:01:39 +0300
Subject: [PATCH 028/446] A secret type must be used for pull secret to work
---
content/en/docs/concepts/configuration/secret.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index fa45f3e017..774dc9a38b 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -684,7 +684,7 @@ for information on referencing service account credentials from within Pods.
### Docker config Secrets
-You can use one of the following `type` values to create a Secret to
+You **MUST** use one of the following `type` values to create a Secret to
store the credentials for accessing a container image registry:
- `kubernetes.io/dockercfg`
From 807103fc21a5a75b4f028ef63142cd8935670b4e Mon Sep 17 00:00:00 2001
From: Mike Mwanje
Date: Wed, 28 Jun 2023 16:48:27 +0000
Subject: [PATCH 029/446] Replace data with stringData in TLS secret example
---
content/en/docs/concepts/configuration/secret.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index fa45f3e017..182859de22 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -854,7 +854,7 @@ kind: Secret
metadata:
name: secret-tls
type: kubernetes.io/tls
-data:
+stringData:
# the data is abbreviated in this example
tls.crt: |
MIIC2DCCAcCgAwIBAgIBATANBgkqh ...
From 26490692703252eb65ed70833ad94959c4211a89 Mon Sep 17 00:00:00 2001
From: Mike Mwanje
Date: Wed, 28 Jun 2023 17:11:31 +0000
Subject: [PATCH 030/446] add explanation on when to use each of 'data' and
'stringData' fields
---
content/en/docs/concepts/configuration/secret.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index 182859de22..f89762c548 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -846,6 +846,8 @@ When using this type of Secret, the `tls.key` and the `tls.crt` key must be prov
in the `data` (or `stringData`) field of the Secret configuration, although the API
server doesn't actually validate the values for each key.
+Use the `stringData` field to add the certificate and private key directly to the secret. Use the `data` field to provide base64 encoded values of both the certificate and private key. Refer to [Constraints on Secret names and data](#restriction-names-data) for more on this.
+
The following YAML contains an example config for a TLS Secret:
```yaml
From 3e0e88dadc10059a467f371682d0377398434dc1 Mon Sep 17 00:00:00 2001
From: Francesco Romani
Date: Thu, 29 Jun 2023 14:04:46 +0200
Subject: [PATCH 031/446] docs: podresources API is stable
Mark the API, needed to monitor the device plugins, as stable
Signed-off-by: Francesco Romani
---
.../extend-kubernetes/compute-storage-net/device-plugins.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 7722d9ffa8..872f1eb6db 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
@@ -195,7 +195,7 @@ of the device allocations during the upgrade.
## Monitoring device plugin resources
-{{< feature-state for_k8s_version="v1.15" state="beta" >}}
+{{< feature-state for_k8s_version="v1.28" state="stable" >}}
In order to monitor resources provided by device plugins, monitoring agents need to be able to
discover the set of devices that are in-use on the node and obtain metadata to describe which
From b6ae4315910aca177f010c4e791dbbe553d4d920 Mon Sep 17 00:00:00 2001
From: Mike Mwanje
Date: Thu, 29 Jun 2023 15:05:31 +0000
Subject: [PATCH 032/446] improve explanation on when to use 'data' and
'stringData' fields
---
content/en/docs/concepts/configuration/secret.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index f89762c548..aa42ff398d 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -846,7 +846,7 @@ When using this type of Secret, the `tls.key` and the `tls.crt` key must be prov
in the `data` (or `stringData`) field of the Secret configuration, although the API
server doesn't actually validate the values for each key.
-Use the `stringData` field to add the certificate and private key directly to the secret. Use the `data` field to provide base64 encoded values of both the certificate and private key. Refer to [Constraints on Secret names and data](#restriction-names-data) for more on this.
+As an alternative to using `stringData`, you can use the `data` field to provide the base64 encoded certificate and private key. Refer to [Constraints on Secret names and data](#restriction-names-data) for more on this.
The following YAML contains an example config for a TLS Secret:
From 0066c6b685221e25efdf9126508ec1d7fd14793b Mon Sep 17 00:00:00 2001
From: Mike Mwanje
Date: Thu, 29 Jun 2023 16:13:47 +0000
Subject: [PATCH 033/446] remove misleading note
---
.../en/docs/concepts/configuration/secret.md | 19 ++++---------------
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index aa42ff398d..857564351b 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -859,8 +859,10 @@ type: kubernetes.io/tls
stringData:
# the data is abbreviated in this example
tls.crt: |
+ --------BEGIN CERTIFICATE-----
MIIC2DCCAcCgAwIBAgIBATANBgkqh ...
tls.key: |
+ -----BEGIN RSA PRIVATE KEY-----
MIIEpgIBAAKCAQEA7yn3bRHQ5FHMQ ...
```
@@ -878,21 +880,8 @@ kubectl create secret tls my-tls-secret \
--key=path/to/key/file
```
-The public/private key pair must exist before hand. The public key certificate
-for `--cert` must be DER format as per
-[Section 5.1 of RFC 7468](https://datatracker.ietf.org/doc/html/rfc7468#section-5.1),
-and must match the given private key for `--key` (PKCS #8 in DER format;
-[Section 11 of RFC 7468](https://datatracker.ietf.org/doc/html/rfc7468#section-11)).
-
-{{< note >}}
-A kubernetes.io/tls Secret stores the Base64-encoded DER data for keys and
-certificates. If you're familiar with PEM format for private keys and for certificates,
-the base64 data are the same as that format except that you omit
-the initial and the last lines that are used in PEM.
-
-For example, for a certificate, you do **not** include `--------BEGIN CERTIFICATE-----`
-and `-------END CERTIFICATE----`.
-{{< /note >}}
+The public/private key pair must exist before hand. The public key certificate for `--cert` must be .PEM encoded
+and must match the given private key for `--key`.
### Bootstrap token Secrets
From b6877e21c3ef00741cdf6d6b54eb147f2b61ce3c Mon Sep 17 00:00:00 2001
From: Dan Winship
Date: Mon, 8 May 2023 15:34:39 -0400
Subject: [PATCH 034/446] KEP-3453 to GA
---
.../feature-gates.md | 5 +--
.../docs/reference/networking/virtual-ips.md | 36 +++++++++----------
2 files changed, 19 insertions(+), 22 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 6d70ba7544..fa80088fd8 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
@@ -147,8 +147,6 @@ 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 | |
-| `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 | |
@@ -295,6 +293,9 @@ For a reference to old feature gates that are removed, please refer to
| `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
| `LegacyServiceAccountTokenTracking` | `true` | Beta | 1.27 | 1.27 |
| `LegacyServiceAccountTokenTracking` | `true` | GA | 1.28 | - |
+| `MinimizeIPTablesRestore` | `false` | Alpha | 1.26 | 1.26 |
+| `MinimizeIPTablesRestore` | `true` | Beta | 1.27 | 1.27 |
+| `MinimizeIPTablesRestore` | `true` | GA | 1.28 | - |
| `MixedProtocolLBService` | `false` | Alpha | 1.20 | 1.23 |
| `MixedProtocolLBService` | `true` | Beta | 1.24 | 1.25 |
| `MixedProtocolLBService` | `true` | GA | 1.26 | - |
diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index 6317a9d7c5..c7ac672aad 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -138,26 +138,6 @@ 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
@@ -189,6 +169,22 @@ 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.
+##### Updating legacy `minSyncPeriod` configuration {#minimize-iptables-restore}
+
+Older versions of kube-proxy updated all the rules for all Services on
+every sync; this led to performance issues (update lag) in large
+clusters, and the recommended solution was to set a larger
+`minSyncPeriod`. Since Kubernetes v1.28, the iptables mode of
+kube-proxy uses a more minimal approach, only making updates where
+Services or EndpointSlices have actually changed.
+
+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.
+
+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.
+
##### `syncPeriod`
The `syncPeriod` parameter controls a handful of synchronization
From e051ea88e8b03a012c13877cd045fe0862fbf56f Mon Sep 17 00:00:00 2001
From: Heba Elayoty
Date: Mon, 3 Jul 2023 08:24:20 -0700
Subject: [PATCH 038/446] Update docs with new job annotation
Signed-off-by: Heba Elayoty
---
.../docs/reference/labels-annotations-taints/_index.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 9f3b08b349..e6c4266a1f 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -1042,6 +1042,16 @@ Used on: Pod
The Job controller in the kube-controller-manager sets this annotation for Pods
created with Indexed [completion mode](/docs/concepts/workloads/controllers/job/#completion-mode).
+### batch.kubernetes.io/cronjob-scheduled-timestamp
+
+Type: Annotation
+
+Example: `batch.kubernetes.io/cronjob-scheduled-timestamp: "2016-05-19T03:00:00-07:00"`
+
+Used on: Jobs and Pods controlled by Jobs
+
+This annotation is used to record the original/expected creation timestamp for the running job. It is represented in RFC3339.
+
### kubectl.kubernetes.io/default-container
Type: Annotation
From 5f81e345fc32c12e126980a0a66e334ea2539c3f Mon Sep 17 00:00:00 2001
From: Heba Elayoty <31887807+helayoty@users.noreply.github.com>
Date: Mon, 3 Jul 2023 13:15:06 -0700
Subject: [PATCH 039/446] Update
content/en/docs/reference/labels-annotations-taints/_index.md
Co-authored-by: Tim Bannister
---
content/en/docs/reference/labels-annotations-taints/_index.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index e6c4266a1f..6f42b4800a 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -1050,7 +1050,9 @@ Example: `batch.kubernetes.io/cronjob-scheduled-timestamp: "2016-05-19T03:00:00-
Used on: Jobs and Pods controlled by Jobs
-This annotation is used to record the original/expected creation timestamp for the running job. It is represented in RFC3339.
+This annotation is used to record the original (expected) creation timestamp for a Job,
+when that Job is part of a CronJob.
+The control plane sets the value to that timestamp in RFC3339 format.
### kubectl.kubernetes.io/default-container
From 16ff7310a8da71d91a3431515fe0e20ee9cb1db3 Mon Sep 17 00:00:00 2001
From: Heba Elayoty <31887807+helayoty@users.noreply.github.com>
Date: Mon, 3 Jul 2023 13:15:23 -0700
Subject: [PATCH 040/446] Update
content/en/docs/reference/labels-annotations-taints/_index.md
Co-authored-by: Tim Bannister
---
content/en/docs/reference/labels-annotations-taints/_index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 6f42b4800a..7e2c840b75 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -1048,7 +1048,7 @@ Type: Annotation
Example: `batch.kubernetes.io/cronjob-scheduled-timestamp: "2016-05-19T03:00:00-07:00"`
-Used on: Jobs and Pods controlled by Jobs
+Used on: Jobs and Pods controlled by CronJobs
This annotation is used to record the original (expected) creation timestamp for a Job,
when that Job is part of a CronJob.
From e003b027b1af10aa09489760e4e553f31faf90cb Mon Sep 17 00:00:00 2001
From: Shubham
Date: Tue, 4 Jul 2023 08:20:52 +0530
Subject: [PATCH 041/446] Move Feature Gate AdvancedAuditing to Feature Gates
(removed) Page (#41693)
* Move Feature Gate AdvancedAuditing under Feature Gates (removed) Page.
* Corrected the GA version.
---
.../command-line-tools-reference/feature-gates-removed.md | 5 +++++
.../reference/command-line-tools-reference/feature-gates.md | 4 ----
2 files changed, 5 insertions(+), 4 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 7cfad6315d..1e55b9e10d 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
@@ -32,6 +32,9 @@ In the following table:
|---------|---------|-------|-------|-------|
| `Accelerators` | `false` | Alpha | 1.6 | 1.10 |
| `Accelerators` | - | Deprecated | 1.11 | 1.11 |
+| `AdvancedAuditing` | `false` | Alpha | 1.7 | 1.7 |
+| `AdvancedAuditing` | `true` | Beta | 1.8 | 1.11 |
+| `AdvancedAuditing` | `true` | GA | 1.12 | 1.27 |
| `AffinityInAnnotations` | `false` | Alpha | 1.6 | 1.7 |
| `AffinityInAnnotations` | - | Deprecated | 1.8 | 1.8 |
| `AllowExtTrafficLocalEndpoints` | `false` | Beta | 1.4 | 1.6 |
@@ -396,6 +399,8 @@ In the following table:
- `AffinityInAnnotations`: Enable setting
[Pod affinity or anti-affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity).
+- `AdvancedAuditing`: Enable [advanced auditing](/docs/tasks/debug/debug-cluster/audit/#advanced-audit)
+
- `AllowExtTrafficLocalEndpoints`: Enable a service to route external requests to node local endpoints.
- `AllowInsecureBackendProxy`: Enable the users to skip TLS verification of
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 6d70ba7544..be6ea04cee 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
@@ -224,9 +224,6 @@ For a reference to old feature gates that are removed, please refer to
| Feature | Default | Stage | Since | Until |
|---------|---------|-------|-------|-------|
-| `AdvancedAuditing` | `false` | Alpha | 1.7 | 1.7 |
-| `AdvancedAuditing` | `true` | Beta | 1.8 | 1.11 |
-| `AdvancedAuditing` | `true` | GA | 1.12 | - |
| `APISelfSubjectReview` | `false` | Alpha | 1.26 | 1.26 |
| `APISelfSubjectReview` | `true` | Beta | 1.27 | 1.27 |
| `APISelfSubjectReview` | `true` | GA | 1.28 | - |
@@ -390,7 +387,6 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `APIServerIdentity`: Assign each API server an ID in a cluster, using a [Lease](/docs/concepts/architecture/leases).
- `APIServerTracing`: Add support for distributed tracing in the API server.
See [Traces for Kubernetes System Components](/docs/concepts/cluster-administration/system-traces) for more details.
-- `AdvancedAuditing`: Enable [advanced auditing](/docs/tasks/debug/debug-cluster/audit/#advanced-audit)
- `AggregatedDiscoveryEndpoint`: Enable a single HTTP endpoint `/discovery/` which
supports native HTTP caching with ETags containing all APIResources known to the API server.
- `AnyVolumeDataSource`: Enable use of any custom resource as the `DataSource` of a
From 2873cf7beab32c1b7abd0eb154f07c87789784f0 Mon Sep 17 00:00:00 2001
From: Heba Elayoty
Date: Thu, 6 Jul 2023 07:59:26 -0700
Subject: [PATCH 042/446] Add timezone information
Signed-off-by: Heba Elayoty
---
content/en/docs/reference/labels-annotations-taints/_index.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 7e2c840b75..7941ed00a4 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -1052,7 +1052,8 @@ Used on: Jobs and Pods controlled by CronJobs
This annotation is used to record the original (expected) creation timestamp for a Job,
when that Job is part of a CronJob.
-The control plane sets the value to that timestamp in RFC3339 format.
+The control plane sets the value to that timestamp in RFC3339 format. The timezone for
+that timestamp is either the explicit timezone in the cronjob or the controller-manager's local time.
### kubectl.kubernetes.io/default-container
From 7386d87bc8f99103d9d3ea11ea539142dfe10dce Mon Sep 17 00:00:00 2001
From: Vikash KUmar Yadav
Date: Fri, 7 Jul 2023 00:07:39 +0530
Subject: [PATCH 043/446] fixed the grammatical mistake in hi docs
---
README-hi.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README-hi.md b/README-hi.md
index da5141af1d..af64eae8f7 100644
--- a/README-hi.md
+++ b/README-hi.md
@@ -3,11 +3,11 @@
[](https://travis-ci.org/kubernetes/website)
[](https://github.com/kubernetes/website/releases/latest)
-स्वागत हे! इस रिपॉजिटरी में [कुबरनेट्स वेबसाइट और दस्तावेज](https://kubernetes.io/) बनाने के लिए आवश्यक सभी संपत्तियां हैं। हम बहुत खुश हैं कि आप योगदान करना चाहते हैं!
+स्वागत है! इस रिपॉजिटरी में [कुबरनेट्स वेबसाइट और दस्तावेज़](https://kubernetes.io/) बनाने के लिए आवश्यक सभी संपत्तियां हैं। हम बहुत खुश हैं कि आप योगदान करना चाहते हैं!
## डॉक्स में योगदान देना
-आप अपने GitHub खाते में इस रिपॉजिटरी की एक copy बनाने के लिए स्क्रीन के ऊपरी-दाएँ क्षेत्र में **Fork** बटन पर क्लिक करें। इस copy को *Fork* कहा जाता है। अपने fork में परिवर्तन करने के बाद जब आप उनको हमारे पास भेजने के लिए तैयार हों, तो अपने fork पर जाएं और हमें इसके बारे में बताने के लिए एक नया pull request बनाएं।
+आप अपने GitHub खाते में इस रिपॉजिटरी की एक copy बनाने के लिए स्क्रीन के ऊपरी-दाएँ क्षेत्र में **Fork** बटन पर क्लिक करें। इस copy को *Fork* कहा जाता है। अपने fork में परिवर्तन करने के बाद जब आप उनको हमारे पास भेजने के लिए तैयार हों, तो अपने fork पर जाएँ और हमें इसके बारे में बताने के लिए एक नया pull request बनाएं।
एक बार जब आपका pull request बन जाता है, तो एक कुबरनेट्स समीक्षक स्पष्ट, कार्रवाई योग्य प्रतिक्रिया प्रदान करने की जिम्मेदारी लेगा। pull request के मालिक के रूप में, **यह आपकी जिम्मेदारी है कि आप कुबरनेट्स समीक्षक द्वारा प्रदान की गई प्रतिक्रिया को संबोधित करने के लिए अपने pull request को संशोधित करें।**
From 0659bf33800494f6410797ecca37ca1b30271469 Mon Sep 17 00:00:00 2001
From: Heba Elayoty
Date: Thu, 6 Jul 2023 12:24:08 -0700
Subject: [PATCH 044/446] Update timezone comment
Signed-off-by: Heba Elayoty
---
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 7941ed00a4..ca2ade313f 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -1052,8 +1052,8 @@ Used on: Jobs and Pods controlled by CronJobs
This annotation is used to record the original (expected) creation timestamp for a Job,
when that Job is part of a CronJob.
-The control plane sets the value to that timestamp in RFC3339 format. The timezone for
-that timestamp is either the explicit timezone in the cronjob or the controller-manager's local time.
+The control plane sets the value to that timestamp in RFC3339 format. If the Job belongs to a CronJob
+with a timezone specified, then the timestamp is in that timezone. Otherwise, the timestamp is in controller-manager's local time.
### kubectl.kubernetes.io/default-container
From aa0617fc3b87826660a2fa596ee43bf43b554a75 Mon Sep 17 00:00:00 2001
From: Craig Comstock
Date: Fri, 7 Jul 2023 15:15:19 -0500
Subject: [PATCH 045/446] Fixed "Show the app in the terminal" URL
The app is listening on port 8080 so that must be included otherwise port 80 (default) is used and the curl request will fail.
Issue: 41259
---
.../docs/tutorials/kubernetes-basics/explore/explore-intro.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt-br/docs/tutorials/kubernetes-basics/explore/explore-intro.html b/content/pt-br/docs/tutorials/kubernetes-basics/explore/explore-intro.html
index e6746bfa8d..9e3e00bbb9 100644
--- a/content/pt-br/docs/tutorials/kubernetes-basics/explore/explore-intro.html
+++ b/content/pt-br/docs/tutorials/kubernetes-basics/explore/explore-intro.html
@@ -267,7 +267,7 @@ description: |-
Para ver a saída da aplicação, execute uma requisição com o comando
curl:
From 8bffe524aad43c71fba5d92c3ac82a00dba0f90b Mon Sep 17 00:00:00 2001
From: windsonsea
Date: Wed, 11 Jan 2023 12:48:17 +0800
Subject: [PATCH 046/446] Fix some layout issues in 12-15 blog
---
.../index.md | 52 +++++++++----------
1 file changed, 26 insertions(+), 26 deletions(-)
diff --git a/content/en/blog/_posts/2022-12-15-dynamic-resource-allocation-alpha/index.md b/content/en/blog/_posts/2022-12-15-dynamic-resource-allocation-alpha/index.md
index 457b8a9721..ac3d34df80 100644
--- a/content/en/blog/_posts/2022-12-15-dynamic-resource-allocation-alpha/index.md
+++ b/content/en/blog/_posts/2022-12-15-dynamic-resource-allocation-alpha/index.md
@@ -5,7 +5,7 @@ date: 2022-12-15
slug: dynamic-resource-allocation
---
- **Authors:** Patrick Ohly (Intel), Kevin Klues (NVIDIA)
+**Authors:** Patrick Ohly (Intel), Kevin Klues (NVIDIA)
Dynamic resource allocation is a new API for requesting resources. It is a
generalization of the persistent volumes API for generic resources, making it possible to:
@@ -19,11 +19,11 @@ Third-party resource drivers are responsible for interpreting these parameters
as well as tracking and allocating resources as requests come in.
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"
-term_id="api-group" >}} are enabled. For details, see the
-`--feature-gates` and `--runtime-config` [kube-apiserver
+`DynamicResourceAllocation`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) and the
+`resource.k8s.io/v1alpha1`
+{{< glossary_tooltip text="API group" term_id="api-group" >}} are enabled. For details,
+see the `--feature-gates` and `--runtime-config` [kube-apiserver
parameters](/docs/reference/command-line-tools-reference/kube-apiserver/).
The kube-scheduler, kube-controller-manager and kubelet components all need
the feature gate enabled as well.
@@ -39,8 +39,8 @@ for end-to-end testing, but also can be run manually. See
## API
-The new `resource.k8s.io/v1alpha1` {{< glossary_tooltip text="API group"
-term_id="api-group" >}} provides four new types:
+The new `resource.k8s.io/v1alpha1` {{< glossary_tooltip text="API group" term_id="api-group" >}}
+provides four new types:
ResourceClass
: Defines which resource driver handles a certain kind of
@@ -77,7 +77,7 @@ this `.spec` (for example, inside a Deployment or StatefulSet) share the same
ResourceClaim instance. When referencing a ResourceClaimTemplate, each Pod gets
its own ResourceClaim instance.
-For a container defined within a Pod, the `resources.claims` list
+For a container defined within a Pod, the `resources.claims` list
defines whether that container gets
access to these resource instances, which makes it possible to share resources
between one or more containers inside the same Pod. For example, an init container could
@@ -89,7 +89,7 @@ will get created for this Pod and each container gets access to one of them.
Assuming a resource driver called `resource-driver.example.com` was installed
together with the following resource class:
-```
+```yaml
apiVersion: resource.k8s.io/v1alpha1
kind: ResourceClass
name: resource.example.com
@@ -151,8 +151,7 @@ spec:
In contrast to native resources (such as CPU or RAM) and
[extended resources](/docs/concepts/configuration/manage-resources-containers/#extended-resources)
-(managed by a
-device plugin, advertised by kubelet), the scheduler has no knowledge of what
+(managed by a device plugin, advertised by kubelet), the scheduler has no knowledge of what
dynamic resources are available in a cluster or how they could be split up to
satisfy the requirements of a specific ResourceClaim. Resource drivers are
responsible for that. Drivers mark ResourceClaims as _allocated_ once resources
@@ -227,8 +226,8 @@ It is up to the driver developer to decide how these two components
communicate. The [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3063-dynamic-resource-allocation/README.md) outlines an [approach using
CRDs](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3063-dynamic-resource-allocation#implementing-a-plugin-for-node-resources).
-Within SIG Node, we also plan to provide a complete [example
-driver](https://github.com/kubernetes-sigs/dra-example-driver) that can serve
+Within SIG Node, we also plan to provide a complete
+[example driver](https://github.com/kubernetes-sigs/dra-example-driver) that can serve
as a template for other drivers.
## Running the test driver
@@ -236,7 +235,7 @@ as a template for other drivers.
The following steps bring up a local, one-node cluster directly from the
Kubernetes source code. As a prerequisite, your cluster must have nodes with a container
runtime that supports the
-[Container Device Interface](https://github.com/container-orchestrated-devices/container-device-interface)
+[Container Device Interface](https://github.com/container-orchestrated-devices/container-device-interface)
(CDI). For example, you can run CRI-O [v1.23.2](https://github.com/cri-o/cri-o/releases/tag/v1.23.2) or later.
Once containerd v1.7.0 is released, we expect that you can run that or any later version.
In the example below, we use CRI-O.
@@ -259,15 +258,16 @@ $ RUNTIME_CONFIG=resource.k8s.io/v1alpha1 \
PATH=$(pwd)/third_party/etcd:$PATH \
./hack/local-up-cluster.sh -O
...
-To start using your cluster, you can open up another terminal/tab and run:
-
- export KUBECONFIG=/var/run/kubernetes/admin.kubeconfig
-...
```
-Once the cluster is up, in another
-terminal run the test driver controller. `KUBECONFIG` must be set for all of
-the following commands.
+To start using your cluster, you can open up another terminal/tab and run:
+
+```console
+$ export KUBECONFIG=/var/run/kubernetes/admin.kubeconfig
+```
+
+Once the cluster is up, in another terminal run the test driver controller.
+`KUBECONFIG` must be set for all of the following commands.
```console
$ go run ./test/e2e/dra/test-driver --feature-gates ContextualLogging=true -v=5 controller
@@ -319,7 +319,7 @@ user_a='b'
## Next steps
- See the
-[Dynamic Resource Allocation](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3063-dynamic-resource-allocation/README.md)
+ [Dynamic Resource Allocation](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3063-dynamic-resource-allocation/README.md)
KEP for more information on the design.
- Read [Dynamic Resource Allocation](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/)
in the official Kubernetes documentation.
@@ -328,6 +328,6 @@ user_a='b'
and / or the [CNCF Container Orchestrated Device Working Group](https://github.com/cncf/tag-runtime/blob/master/wg/COD.md).
- You can view or comment on the [project board](https://github.com/orgs/kubernetes/projects/95/views/1)
for dynamic resource allocation.
- - In order to move this feature towards beta, we need feedback from hardware
- vendors, so here's a call to action: try out this feature, consider how it can help
- with problems that your users are having, and write resource drivers…
+- In order to move this feature towards beta, we need feedback from hardware
+ vendors, so here's a call to action: try out this feature, consider how it can help
+ with problems that your users are having, and write resource drivers…
From c2ad478632b08d97e341c9dfd571f623789ca147 Mon Sep 17 00:00:00 2001
From: sravyasambaturu <71900458+sravyasambaturu@users.noreply.github.com>
Date: Sat, 8 Jul 2023 22:31:21 +0530
Subject: [PATCH 047/446] updating cluster-intro.html #line89
---
.../kubernetes-basics/create-cluster/cluster-intro.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html b/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html
index 122ed7346e..cc988c9d0e 100644
--- a/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html
+++ b/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html
@@ -86,7 +86,7 @@ description: |-
-
When you deploy applications on Kubernetes, you tell the control plane to start the application containers. The control plane schedules the containers to run on the cluster's nodes. The nodes communicate with the control plane using the Kubernetes API, which the control plane exposes. End users can also use the Kubernetes API directly to interact with the cluster.
+
When you deploy applications on Kubernetes, you tell the control plane to start the application containers. The control plane schedules the containers to run on the cluster's nodes. The kubelet on each node communicates with the control plane using the Kubernetes API, which the control plane exposes. End users can also use the Kubernetes API directly to interact with the cluster.
A Kubernetes cluster can be deployed on either physical or virtual machines. To get started with Kubernetes development, you can use Minikube. Minikube is a lightweight Kubernetes implementation that creates a VM on your local machine and deploys a simple cluster containing only one node. Minikube is available for Linux, macOS, and Windows systems. The Minikube CLI provides basic bootstrapping operations for working with your cluster, including start, stop, status, and delete.
When you deploy applications on Kubernetes, you tell the control plane to start the application containers. The control plane schedules the containers to run on the cluster's nodes. The kubelet on each node communicates with the control plane using the Kubernetes API, which the control plane exposes. End users can also use the Kubernetes API directly to interact with the cluster.
+
When you deploy applications on Kubernetes, you tell the control plane to start the application containers. The control plane schedules the containers to run on the cluster's nodes. Node-level components, such as the kubelet, communicate with the control plane using the Kubernetes API, which the control plane exposes. End users can also use the Kubernetes API directly to interact with the cluster.
A Kubernetes cluster can be deployed on either physical or virtual machines. To get started with Kubernetes development, you can use Minikube. Minikube is a lightweight Kubernetes implementation that creates a VM on your local machine and deploys a simple cluster containing only one node. Minikube is available for Linux, macOS, and Windows systems. The Minikube CLI provides basic bootstrapping operations for working with your cluster, including start, stop, status, and delete.
When set to true, --interactive flag in kubectl delete command will be activated and by passing this flag, users can preview and confirm resources before proceeding to delete.
+
+
+
From 810a320a4873dcb3bfb12db39edd4aa215c46af8 Mon Sep 17 00:00:00 2001
From: Roman Bednar
Date: Thu, 18 May 2023 11:44:22 +0200
Subject: [PATCH 050/446] graduate RetroactiveDefaultStorageClass feature to GA
in 1.28
---
content/en/docs/concepts/storage/persistent-volumes.md | 2 +-
.../reference/command-line-tools-reference/feature-gates.md | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index ca68c365ee..dfa08602f8 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -876,7 +876,7 @@ it won't be supported in a future Kubernetes release.
#### Retroactive default StorageClass assignment
-{{< feature-state for_k8s_version="v1.26" state="beta" >}}
+{{< feature-state for_k8s_version="v1.28" state="stable" >}}
You can create a PersistentVolumeClaim without specifying a `storageClassName`
for the new PVC, and you can do so even when no default StorageClass exists
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 be6ea04cee..7b6fd36168 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,8 +183,6 @@ For a reference to old feature gates that are removed, please refer to
| `RecoverVolumeExpansionFailure` | `false` | Alpha | 1.23 | |
| `RemainingItemCount` | `false` | Alpha | 1.15 | 1.15 |
| `RemainingItemCount` | `true` | Beta | 1.16 | |
-| `RetroactiveDefaultStorageClass` | `false` | Alpha | 1.25 | 1.25 |
-| `RetroactiveDefaultStorageClass` | `true` | Beta | 1.26 | |
| `RotateKubeletServerCertificate` | `false` | Alpha | 1.7 | 1.11 |
| `RotateKubeletServerCertificate` | `true` | Beta | 1.12 | |
| `SELinuxMountReadWriteOncePod` | `false` | Alpha | 1.25 | 1.26 |
@@ -304,6 +302,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 | - |
+| `RetroactiveDefaultStorageClass` | `false` | Alpha | 1.25 | 1.25 |
+| `RetroactiveDefaultStorageClass` | `true` | Beta | 1.26 | 1.27 |
+| `RetroactiveDefaultStorageClass` | `true` | GA | 1.28 | - |
| `SeccompDefault` | `false` | Alpha | 1.22 | 1.24 |
| `SeccompDefault` | `true` | Beta | 1.25 | 1.26 |
| `SeccompDefault` | `true` | GA | 1.27 | - |
From cecd565f90ef2bc2d3ddc8facd15faeb46d6b604 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Arda=20G=C3=BC=C3=A7l=C3=BC?=
Date: Wed, 12 Jul 2023 08:26:16 +0300
Subject: [PATCH 051/446] Update environment variable description
---
content/en/docs/reference/kubectl/kubectl.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/reference/kubectl/kubectl.md b/content/en/docs/reference/kubectl/kubectl.md
index 61f1401db3..8d6e8aae0c 100644
--- a/content/en/docs/reference/kubectl/kubectl.md
+++ b/content/en/docs/reference/kubectl/kubectl.md
@@ -373,7 +373,7 @@ kubectl [flags]
KUBECTL_INTERACTIVE_DELETE
-
When set to true, --interactive flag in kubectl delete command will be activated and by passing this flag, users can preview and confirm resources before proceeding to delete.
+
When set to true, the --interactive flag in the kubectl delete command will be activated, allowing users to preview and confirm resources before proceeding to delete by passing this flag.
From b3af1a9553862ece5adc68c02cfcf456dc1503e2 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Wed, 12 Jul 2023 12:47:25 -0400
Subject: [PATCH 052/446] add a note mentioning the rename in 1.28
---
.../2022-09-14-pod-has-network-condition.md | 42 +++++++++++--------
1 file changed, 24 insertions(+), 18 deletions(-)
diff --git a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
index f19b91e4f9..b78d8dcf53 100644
--- a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
+++ b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
@@ -1,6 +1,6 @@
---
layout: blog
-title: 'Kubernetes 1.25: PodReadyToStartContainers Condition for Pods'
+title: 'Kubernetes 1.25: PodHasNetwork Condition for Pods'
date: 2022-09-14
slug: pod-has-network-condition
---
@@ -9,20 +9,26 @@ slug: pod-has-network-condition
Deep Debroy (Apple)
Kubernetes 1.25 introduces Alpha support for a new kubelet-managed pod condition
-in the status field of a pod: `PodReadyToStartContainers`. The kubelet, for a worker node,
-will use the `PodReadyToStartContainers` condition to accurately surface the initialization
+in the status field of a pod: `PodHasNetwork`. The kubelet, for a worker node,
+will use the `PodHasNetwork` condition to accurately surface the initialization
state of a pod from the perspective of pod sandbox creation and network
configuration by a container runtime (typically in coordination with CNI
plugins). The kubelet starts to pull container images and start individual
-containers (including init containers) after the status of the `PodReadyToStartContainers`
+containers (including init containers) after the status of the `PodHasNetwork`
condition is set to `"True"`. Metrics collection services that report latency of
pod initialization from a cluster infrastructural perspective (i.e. agnostic of
per container characteristics like image size or payload) can utilize the
-`PodReadyToStartContainers` condition to accurately generate Service Level Indicators
+`PodHasNetwork` condition to accurately generate Service Level Indicators
(SLIs). Certain operators or controllers that manage underlying pods may utilize
-the `PodReadyToStartContainers` condition to optimize the set of actions performed when pods
+the `PodHasNetwork` condition to optimize the set of actions performed when pods
repeatedly fail to come up.
+### Updates for Kubernetes 1.28
+
+The PodHasNetwork condition has been renamed to PodReadyToStartContainers.
+To enable this alpha feature you have to set the feature toggle PodReadyToStartContainersCondition
+to true.
+
### How is this different from the existing Initialized condition reported for pods?
The kubelet sets the status of the existing `Initialized` condition reported in
@@ -44,14 +50,14 @@ containers will report the status of the `Initialized` condition as `"True"`
even if the container runtime is not able to successfully initialize the pod
sandbox environment.
-Relative to either situation above, the `PodReadyToStartContainers` condition surfaces more
+Relative to either situation above, the `PodHasNetwork` condition surfaces more
accurate data around when the pod runtime sandbox was initialized with
networking configured so that the kubelet can proceed to launch user-configured
containers (including init containers) in the pod.
### Special Cases
-If a pod specifies `hostNetwork` as `"True"`, the `PodReadyToStartContainers` condition is
+If a pod specifies `hostNetwork` as `"True"`, the `PodHasNetwork` condition is
set to `"True"` based on successful creation of the pod sandbox while the
network configuration state of the pod sandbox is ignored. This is because the
CRI implementation typically skips any pod sandbox network configuration when
@@ -61,17 +67,17 @@ A node agent may dynamically re-configure network interface(s) for a pod by
watching changes in pod annotations that specify additional networking
configuration (e.g. `k8s.v1.cni.cncf.io/networks`). Dynamic updates of pod
networking configuration after the pod sandbox is initialized by Kubelet (in
-coordination with a container runtime) are not reflected by the `PodReadyToStartContainers`
+coordination with a container runtime) are not reflected by the `PodHasNetwork`
condition.
-### Try out the PodReadyToStartContainers condition for pods
+### Try out the PodHasNetwork condition for pods
-In order to have the kubelet report the `PodReadyToStartContainers` condition in the status
-field of a pod, please enable the `PodReadyToStartContainersCondition` feature gate on the
+In order to have the kubelet report the `PodHasNetwork` condition in the status
+field of a pod, please enable the `PodHasNetworkCondition` feature gate on the
kubelet.
For a pod whose runtime sandbox has been successfully created and has networking
-configured, the kubelet will report the `PodReadyToStartContainers` condition with status set to `"True"`:
+configured, the kubelet will report the `PodHasNetwork` condition with status set to `"True"`:
```
$ kubectl describe pod nginx1
@@ -80,7 +86,7 @@ Namespace: default
...
Conditions:
Type Status
- PodReadyToStartContainers True
+ PodHasNetwork True
Initialized True
Ready True
ContainersReady True
@@ -88,7 +94,7 @@ Conditions:
```
For a pod whose runtime sandbox has not been created yet (and networking not
-configured either), the kubelet will report the `PodReadyToStartContainers` condition with
+configured either), the kubelet will report the `PodHasNetwork` condition with
status set to `"False"`:
```
@@ -98,7 +104,7 @@ Namespace: default
...
Conditions:
Type Status
- PodReadyToStartContainers False
+ PodHasNetwork False
Initialized True
Ready False
ContainersReady False
@@ -108,13 +114,13 @@ Conditions:
### What’s next?
Depending on feedback and adoption, the Kubernetes team plans to push the
-reporting of the `PodReadyToStartContainers` condition to Beta in 1.26 or 1.27.
+reporting of the `PodHasNetwork` condition to Beta in 1.26 or 1.27.
### How can I learn more?
Please check out the
[documentation](/docs/concepts/workloads/pods/pod-lifecycle/) for the
-`PodReadyToStartContainers` condition to learn more about it and how it fits in relation to
+`PodHasNetwork` condition to learn more about it and how it fits in relation to
other pod conditions.
### How to get involved?
From 400fbf9cc21f6beb589a03a50a12dab913ea8ec4 Mon Sep 17 00:00:00 2001
From: carlory
Date: Fri, 26 May 2023 00:34:11 +0800
Subject: [PATCH 053/446] add CSIMigrationRBD feature promotion from alpha to
deprecated
---
content/en/docs/concepts/storage/volumes.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/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index 53919d5255..ba04f037a5 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -888,7 +888,7 @@ for more details.
#### RBD CSI migration {#rbd-csi-migration}
-{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
+{{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
The `CSIMigration` feature for `RBD`, when enabled, redirects all plugin
operations from the existing in-tree plugin to the `rbd.csi.ceph.com` {{<
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 be6ea04cee..7fadaa224b 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
@@ -78,7 +78,6 @@ For a reference to old feature gates that are removed, please refer to
| `CPUManagerPolicyOptions` | `true` | Beta | 1.23 | |
| `CSIMigrationPortworx` | `false` | Alpha | 1.23 | 1.24 |
| `CSIMigrationPortworx` | `false` | Beta | 1.25 | |
-| `CSIMigrationRBD` | `false` | Alpha | 1.23 | |
| `CSINodeExpandSecret` | `false` | Alpha | 1.25 | 1.26 |
| `CSINodeExpandSecret` | `true` | Beta | 1.27 | |
| `CSIVolumeHealth` | `false` | Alpha | 1.21 | |
@@ -238,6 +237,8 @@ For a reference to old feature gates that are removed, please refer to
| `CSIMigrationGCE` | `false` | Beta | 1.17 | 1.22 |
| `CSIMigrationGCE` | `true` | Beta | 1.23 | 1.24 |
| `CSIMigrationGCE` | `true` | GA | 1.25 | - |
+| `CSIMigrationRBD` | `false` | Alpha | 1.23 | 1.27 |
+| `CSIMigrationRBD` | `false` | Deprecated | 1.28 | - |
| `CSIMigrationvSphere` | `false` | Alpha | 1.18 | 1.18 |
| `CSIMigrationvSphere` | `false` | Beta | 1.19 | 1.24 |
| `CSIMigrationvSphere` | `true` | Beta | 1.25 | 1.25 |
From b664cb465d6b51db63832a8af64e1ab79f7ebbdb Mon Sep 17 00:00:00 2001
From: Dan Winship
Date: Mon, 17 Jul 2023 10:22:02 -0400
Subject: [PATCH 054/446] IPTablesOwnershipCleanup to GA
---
.../reference/command-line-tools-reference/feature-gates.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 88e2cae5d5..412f05b2fb 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
@@ -108,8 +108,6 @@ 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 | 1.26 |
-| `IPTablesOwnershipCleanup` | `true` | Beta | 1.27 | |
| `InPlacePodVerticalScaling` | `false` | Alpha | 1.27 | |
| `InTreePluginAWSUnregister` | `false` | Alpha | 1.21 | |
| `InTreePluginAzureDiskUnregister` | `false` | Alpha | 1.21 | |
@@ -273,6 +271,9 @@ For a reference to old feature gates that are removed, please refer to
| `GRPCContainerProbe` | `false` | Alpha | 1.23 | 1.23 |
| `GRPCContainerProbe` | `true` | Beta | 1.24 | 1.26 |
| `GRPCContainerProbe` | `true` | GA | 1.27 | |
+| `IPTablesOwnershipCleanup` | `false` | Alpha | 1.25 | 1.26 |
+| `IPTablesOwnershipCleanup` | `true` | Beta | 1.27 | 1.27 |
+| `IPTablesOwnershipCleanup` | `true` | GA | 1.28 | - |
| `JobMutableNodeSchedulingDirectives` | `true` | Beta | 1.23 | 1.26 |
| `JobMutableNodeSchedulingDirectives` | `true` | GA | 1.27 | |
| `JobTrackingWithFinalizers` | `false` | Alpha | 1.22 | 1.22 |
From a0a473ba710d3251ce927792190c6746e764e2d0 Mon Sep 17 00:00:00 2001
From: Sergey Kanzhelev
Date: Mon, 17 Jul 2023 20:30:07 +0000
Subject: [PATCH 055/446] promoted parallel image pulls
---
content/en/docs/concepts/containers/images.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/containers/images.md b/content/en/docs/concepts/containers/images.md
index 627036cde5..48b6b7fd1d 100644
--- a/content/en/docs/concepts/containers/images.md
+++ b/content/en/docs/concepts/containers/images.md
@@ -182,7 +182,7 @@ 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" >}}
+{{< feature-state for_k8s_version="v1.28" state="beta" >}}
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
From 0f66ee54ccf5ac39219eb8614066c44d1621af8c Mon Sep 17 00:00:00 2001
From: Cici Huang
Date: Mon, 17 Jul 2023 00:56:09 -0700
Subject: [PATCH 056/446] Update doc for KEP 2876
---
.../custom-resource-definitions.md | 27 +++++++++++++++++++
1 file changed, 27 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 edade8f825..45095d6b53 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
@@ -1066,6 +1066,33 @@ 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.
+#### The reason and fieldPath fields
+
+Besides the `message` and `messageExpression` fields, which defines the string reported for a validation rule failure,
+we have also added two more fields under `validation`:
+- `reason` field which allows user to specify a machine-readable validation failure reason when a request fails this validation rule.
+- `fieldPath` field which specify the field path returned when the validation fails.
+
+For example:
+
+```yaml
+x-kubernetes-validations:
+- rule: "self.x <= self.maxLimit"
+ messageExpression: '"x exceeded max limit of " + string(self.maxLimit)'
+ reason: "FieldValueInvalid"
+ fieldPath: ".x"
+```
+
+The HTTP status code returned to the caller will match the reason of the reason of the first failed validation rule.
+The currently supported reasons are: "FieldValueInvalid", "FieldValueForbidden", "FieldValueRequired", "FieldValueDuplicate".
+If not set, default to use "FieldValueInvalid".
+
+For `fieldPath`, It must be a relative JSON path scoped to the location of this x-kubernetes-validations extension in the schema and refer to an existing field.
+For example when validation checks if a specific attribute `foo` under a map `testMap`, the fieldPath could be set to `".testMap.foo"` or `.tetsMap['foo']'`.
+If the validation checks two lists must have unique attributes, the fieldPath could be set to either of the list: e.g. `.testList1` or `.testList2`.
+It supports child operation to refer to an existing field currently. Refer to [JSONPath support in Kubernetes](https://kubernetes.io/docs/reference/kubectl/jsonpath/) for more info.
+And it does not support numeric index of array.
+
#### Validation functions {#available-validation-functions}
Functions available include:
From 4391c3b0bc5b89cd770a6babc9f5e30ec71b2aa9 Mon Sep 17 00:00:00 2001
From: Cici Huang
Date: Fri, 21 Jul 2023 17:05:35 +0000
Subject: [PATCH 057/446] Address comments
---
.../custom-resources/custom-resource-definitions.md | 6 +++---
1 file changed, 3 insertions(+), 3 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 45095d6b53..bcf02cdb60 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
@@ -1083,13 +1083,13 @@ x-kubernetes-validations:
fieldPath: ".x"
```
-The HTTP status code returned to the caller will match the reason of the reason of the first failed validation rule.
+The HTTP status code returned to the caller will match the reason of the first failed validation rule.
The currently supported reasons are: "FieldValueInvalid", "FieldValueForbidden", "FieldValueRequired", "FieldValueDuplicate".
If not set, default to use "FieldValueInvalid".
-For `fieldPath`, It must be a relative JSON path scoped to the location of this x-kubernetes-validations extension in the schema and refer to an existing field.
+The `fieldPath` value must be a relative JSON path that is scoped to the location of this x-kubernetes-validations extension in the schema. Additionally, it should refer to an existing field within the schema.
For example when validation checks if a specific attribute `foo` under a map `testMap`, the fieldPath could be set to `".testMap.foo"` or `.tetsMap['foo']'`.
-If the validation checks two lists must have unique attributes, the fieldPath could be set to either of the list: e.g. `.testList1` or `.testList2`.
+If the validation requires checking for unique attributes in two lists, the fieldPath can be set to either of the lists. For example, it can be set to `.testList1` or `.testList2`.
It supports child operation to refer to an existing field currently. Refer to [JSONPath support in Kubernetes](https://kubernetes.io/docs/reference/kubectl/jsonpath/) for more info.
And it does not support numeric index of array.
From 3e3c3aebff9e9d82da9c2bdf3538228cc78e78c4 Mon Sep 17 00:00:00 2001
From: Daniel Vega-Myhre
Date: Sun, 23 Jul 2023 01:15:50 +0000
Subject: [PATCH 058/446] add docs for kep-4017
---
.../docs/concepts/workloads/controllers/job.md | 5 ++++-
.../workloads/controllers/statefulset.md | 13 ++++++++++++-
.../labels-annotations-taints/_index.md | 18 ++++++++++++++++--
3 files changed, 32 insertions(+), 4 deletions(-)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index be6a66c9db..9e8c571fb4 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -278,8 +278,11 @@ Jobs with _fixed completion count_ - that is, jobs that have non null
completion is homologous to each other. Note that Jobs that have null
`.spec.completions` are implicitly `NonIndexed`.
- `Indexed`: the Pods of a Job get an associated completion index from 0 to
- `.spec.completions-1`. The index is available through three mechanisms:
+ `.spec.completions-1`. The index is available through four mechanisms:
- The Pod annotation `batch.kubernetes.io/job-completion-index`.
+ - The Pod label `batch.kubernetes.io/job-completion-index` (for v1.28 and later). Note
+ the feature gate `PodIndexLabel` must be enabled to use this label, and it is enabled
+ by default.
- As part of the Pod hostname, following the pattern `$(job-name)-$(index)`.
When you use an Indexed Job in combination with a
{{< glossary_tooltip term_id="Service" >}}, Pods within the Job can use
diff --git a/content/en/docs/concepts/workloads/controllers/statefulset.md b/content/en/docs/concepts/workloads/controllers/statefulset.md
index bdb0703f7a..d1a775b062 100644
--- a/content/en/docs/concepts/workloads/controllers/statefulset.md
+++ b/content/en/docs/concepts/workloads/controllers/statefulset.md
@@ -156,7 +156,8 @@ regardless of which node it's (re)scheduled on.
For a StatefulSet with N [replicas](#replicas), each Pod in the StatefulSet
will be assigned an integer ordinal, that is unique over the Set. By default,
-pods will be assigned ordinals from 0 up through N-1.
+pods will be assigned ordinals from 0 up through N-1. The StatefulSet controller
+will also add a pod label with this index: `apps.kubernetes.io/pod-index`.
### Start ordinal
@@ -234,6 +235,16 @@ it adds a label, `statefulset.kubernetes.io/pod-name`, that is set to the name o
the Pod. This label allows you to attach a Service to a specific Pod in
the StatefulSet.
+### Pod index label
+
+{{< feature-state for_k8s_version="v1.28" state="beta" >}}
+
+When the StatefulSet {{}} creates a Pod,
+the new Pod is labelled with `apps.kubernetes.io/pod-index`. The value of this label is the ordinal index of
+the Pod. This label allows you to route traffic to a particular pod index, filter logs/metrics
+using the pod index label, and more. Note the feature gate `PodIndexLabel` must be enabled for this
+feature, and it is enabled by default.
+
## Deployment and Scaling Guarantees
* For a StatefulSet with N replicas, when Pods are being deployed, they are created sequentially, in order from {0..N-1}.
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 9f3b08b349..6450607233 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -226,6 +226,20 @@ This annotation is applied to the parent object used to track an ApplySet to ind
tooling manages that ApplySet. Tooling should refuse to mutate ApplySets belonging to other tools.
The value must be in the format `/`.
+### apps.kubernetes.io/pod-index (beta) {#apps-kubernetes.io-pod-index}
+
+Type: Label
+
+Example: `apps.kubernetes.io/pod-index: "0"`
+
+Used on: Pod
+
+When a StatefulSet controller creates a Pod for the StatefulSet, it sets this label on that Pod.
+The value of the label is the ordinal index of the pod being created.
+
+See [Pod Index Label](/docs/concepts/workloads/controllers/statefulset/#pod-index-label)
+in the StatefulSet topic for more details.
+
### cluster-autoscaler.kubernetes.io/safe-to-evict
Type: Annotation
@@ -1033,13 +1047,13 @@ by the cloud-controller-manager.
### batch.kubernetes.io/job-completion-index
-Type: Annotation
+Type: Annotation, Label
Example: `batch.kubernetes.io/job-completion-index: "3"`
Used on: Pod
-The Job controller in the kube-controller-manager sets this annotation for Pods
+The Job controller in the kube-controller-manager sets this as a label and annotation for Pods
created with Indexed [completion mode](/docs/concepts/workloads/controllers/job/#completion-mode).
### kubectl.kubernetes.io/default-container
From efbe80ad0075471be777e96ff94acf949786d00b Mon Sep 17 00:00:00 2001
From: carlory
Date: Wed, 24 May 2023 18:41:21 +0800
Subject: [PATCH 059/446] NodeOutOfServiceVolumeDetach feature update to GA
Co-authored-by: Tim Bannister
---
content/en/docs/concepts/architecture/nodes.md | 4 ++--
.../reference/command-line-tools-reference/feature-gates.md | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md
index fedadc40ef..8cb24b56c1 100644
--- a/content/en/docs/concepts/architecture/nodes.md
+++ b/content/en/docs/concepts/architecture/nodes.md
@@ -571,9 +571,9 @@ the feature is Beta and is enabled by default.
Metrics `graceful_shutdown_start_time_seconds` and `graceful_shutdown_end_time_seconds`
are emitted under the kubelet subsystem to monitor node shutdowns.
-## Non Graceful node shutdown {#non-graceful-node-shutdown}
+## Non-graceful node shutdown handling {#non-graceful-node-shutdown}
-{{< feature-state state="beta" for_k8s_version="v1.26" >}}
+{{< feature-state state="stable" for_k8s_version="v1.28" >}}
A node shutdown action may not be detected by kubelet's Node Shutdown Manager,
either because the command does not trigger the inhibitor locks mechanism used by
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 ba21bf029c..c2639aace8 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
@@ -161,8 +161,6 @@ For a reference to old feature gates that are removed, please refer to
| `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 | |
| `OpenAPIEnums` | `false` | Alpha | 1.23 | 1.23 |
| `OpenAPIEnums` | `true` | Beta | 1.24 | |
@@ -293,6 +291,9 @@ For a reference to old feature gates that are removed, please refer to
| `MixedProtocolLBService` | `false` | Alpha | 1.20 | 1.23 |
| `MixedProtocolLBService` | `true` | Beta | 1.24 | 1.25 |
| `MixedProtocolLBService` | `true` | GA | 1.26 | - |
+| `NodeOutOfServiceVolumeDetach` | `false` | Alpha | 1.24 | 1.25 |
+| `NodeOutOfServiceVolumeDetach` | `true` | Beta | 1.26 | 1.27 |
+| `NodeOutOfServiceVolumeDetach` | `true` | GA | 1.28 | - |
| `OpenAPIV3` | `false` | Alpha | 1.23 | 1.23 |
| `OpenAPIV3` | `true` | Beta | 1.24 | 1.26 |
| `OpenAPIV3` | `true` | GA | 1.27 | - |
From c50c151dc71327602a9e60542db9bf0f707160e9 Mon Sep 17 00:00:00 2001
From: Markus Lehtonen
Date: Wed, 19 Jul 2023 13:12:15 +0300
Subject: [PATCH 060/446] docs: document kubelet cgroup driver detection from
the runtime
Document the KubeletCgroupDriverFromCRI feature gate. Also, add notes of
this feature in parts of the documentation that describe cgroup driver
configuration.
---
.../feature-gates.md | 9 +++++++++
.../container-runtimes.md | 19 +++++++++++++++++++
.../kubeadm/configure-cgroup-driver.md | 7 +++++++
3 files changed, 35 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 88e2cae5d5..9d94802ae7 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,6 +125,7 @@ For a reference to old feature gates that are removed, please refer to
| `JobReadyPods` | `true` | Beta | 1.24 | |
| `KMSv2` | `false` | Alpha | 1.25 | 1.26 |
| `KMSv2` | `true` | Beta | 1.27 | |
+| `KubeletCgroupDriverFromCRI` | `false` | Alpha | 1.28 | |
| `KubeletInUserNamespace` | `false` | Alpha | 1.22 | |
| `KubeletPodResourcesDynamicResources` | `false` | Alpha | 1.27 | |
| `KubeletPodResourcesGet` | `false` | Alpha | 1.27 | |
@@ -559,6 +560,14 @@ Each feature gate is designed for enabling/disabling a specific feature:
The Job controller uses Pod finalizers and a field in the Job status to keep
track of the finished Pods to count towards completion.
- `KMSv2`: Enables KMS v2 API for encryption at rest. See [Using a KMS Provider for data encryption](/docs/tasks/administer-cluster/kms-provider) for more details.
+- `KubeletCgroupDriverFromCRI`: Enable detection of the kubelet cgroup driver
+ configuration option from the CRI. This feature gate requires the user run a
+ container runtime that supports the `RuntimeConfig` CRI call. If both CRI and
+ Kubelet support this feature, the kubelet will ignore the cgroupDriver
+ (--cgroup-driver) configuration option. If the container runtime doesn't
+ support it, the kubelet will fallback to using its cgroupDriver option.
+ See [Configuring a cgroup driver](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver)
+ for more details.
- `KubeletCredentialProviders`: Enable kubelet exec credential providers for
image pull credentials.
- `KubeletInUserNamespace`: Enables support for running kubelet in a
diff --git a/content/en/docs/setup/production-environment/container-runtimes.md b/content/en/docs/setup/production-environment/container-runtimes.md
index 46ffce3bb9..8b50d18365 100644
--- a/content/en/docs/setup/production-environment/container-runtimes.md
+++ b/content/en/docs/setup/production-environment/container-runtimes.md
@@ -157,6 +157,13 @@ Starting with v1.22 and later, when creating a cluster with kubeadm, if the user
the `cgroupDriver` field under `KubeletConfiguration`, kubeadm defaults it to `systemd`.
{{< /note >}}
+{{< note >}}
+Starting with v1.28 and later, with KubeletCgroupDriverFromCRI feature gate
+enabled and a container runtime that supports the RuntimeConfig CRI rpc,
+kubelet will automatically detect the cgroup driver from the runtime and the
+cgroupDriver setting in kubelet configuration is ignored.
+{{< /note >}}
+
If you configure `systemd` as the cgroup driver for the kubelet, you must also
configure `systemd` as the cgroup driver for the container runtime. Refer to
the documentation for your container runtime for instructions. For example:
@@ -251,6 +258,12 @@ sudo systemctl restart containerd
When using kubeadm, manually configure the
[cgroup driver for kubelet](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/#configuring-the-kubelet-cgroup-driver).
+{{< note >}}
+Starting with v1.28 and later, kubelet cgroup driver does not need to be
+configured if the KubeletCgroupDriverFromCRI feature gate is enabled and a
+version of containerd that supports the RuntimeConfig CRI rpc is being used.
+{{< /note >}}
+
#### Overriding the sandbox (pause) image {#override-pause-image-containerd}
In your [containerd config](https://github.com/containerd/containerd/blob/main/docs/cri/config.md) you can overwrite the
@@ -292,6 +305,12 @@ You should also note the changed `conmon_cgroup`, which has to be set to the val
cgroup driver configuration of the kubelet (usually done via kubeadm) and CRI-O
in sync.
+{{< note >}}
+Starting with v1.28 and later, kubelet cgroup driver does not need to be
+configured if the KubeletCgroupDriverFromCRI feature gate is enabled and a
+version of CRI-O that supports the RuntimeConfig CRI rpc is being used.
+{{< /note >}}
+
For CRI-O, the CRI socket is `/var/run/crio/crio.sock` by default.
#### Overriding the sandbox (pause) image {#override-pause-image-cri-o}
diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
index f4308c2b0e..9c65eb67a7 100644
--- a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
+++ b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
@@ -38,6 +38,13 @@ In v1.22 and later, if the user does not set the `cgroupDriver` field under `Kub
kubeadm defaults it to `systemd`.
{{< /note >}}
+{{< note >}}
+In v1.28 and later, with KubeletCgroupDriverFromCRI feature gate
+enabled and a container runtime that supports the RuntimeConfig CRI rpc,
+kubelet will automatically detect the cgroup driver from the runtime and the
+kubelet cgroup driver setting does not need to be manually configured.
+{{< /note >}}
+
A minimal example of configuring the field explicitly:
```yaml
From bd9fed6316414d7cebb589841d9a06635af48bce Mon Sep 17 00:00:00 2001
From: pprokop
Date: Mon, 24 Jul 2023 10:41:53 +0200
Subject: [PATCH 061/446] [topologymanager] whitespace cleanup
Signed-off-by: pprokop
---
.../tasks/administer-cluster/topology-manager.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/en/docs/tasks/administer-cluster/topology-manager.md b/content/en/docs/tasks/administer-cluster/topology-manager.md
index 7d06ebe14c..2d20619d84 100644
--- a/content/en/docs/tasks/administer-cluster/topology-manager.md
+++ b/content/en/docs/tasks/administer-cluster/topology-manager.md
@@ -28,7 +28,7 @@ disjoint set of components.
_Topology Manager_ is a Kubelet component that aims to coordinate the set of components that are
responsible for these optimizations.
-
+
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
@@ -174,7 +174,7 @@ each Hint Provider to discover their resource availability. Using this informati
Manager stores the preferred NUMA Node affinity for that container. If the affinity is not
preferred, Topology Manager will store this and admit the pod to the node anyway.
-The *Hint Providers* can then use this information when making the
+The *Hint Providers* can then use this information when making the
resource allocation decision.
### restricted policy {#policy-restricted}
@@ -190,7 +190,7 @@ reschedule the pod. It is recommended to use a ReplicaSet or Deployment to trigg
the pod. An external control loop could be also implemented to trigger a redeployment of pods that
have the `Topology Affinity` error.
-If the pod is admitted, the *Hint Providers* can then use this information when making the
+If the pod is admitted, the *Hint Providers* can then use this information when making the
resource allocation decision.
### single-numa-node policy {#policy-single-numa-node}
@@ -318,7 +318,7 @@ spec:
This pod runs in the `BestEffort` QoS class because there are no CPU and memory requests.
The Topology Manager would consider the above pods. The Topology Manager would consult the Hint
-Providers, which are CPU and Device Manager to get topology hints for the pods.
+Providers, which are CPU and Device Manager to get topology hints for the pods.
In the case of the `Guaranteed` pod with integer CPU request, the `static` CPU Manager policy
would return topology hints relating to the exclusive CPU and the Device Manager would send back
@@ -337,7 +337,7 @@ of the requested devices.
Using this information the Topology Manager calculates the optimal hint for the pod and stores
this information, which will be used by the Hint Providers when they are making their resource
-assignments.
+assignments.
### Known Limitations
@@ -346,4 +346,4 @@ assignments.
generating their hints.
2. The scheduler is not topology-aware, so it is possible to be scheduled on a node and then fail
- on the node due to the Topology Manager.
+ on the node due to the Topology Manager.
\ No newline at end of file
From afbe795bdbe6aa08bcefcd1ce999f81fa6990599 Mon Sep 17 00:00:00 2001
From: pprokop
Date: Wed, 21 Jun 2023 16:36:34 +0200
Subject: [PATCH 062/446] Move TopologyManagerPolicyOptions to beta
Signed-off-by: pprokop
---
.../tasks/administer-cluster/topology-manager.md | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/content/en/docs/tasks/administer-cluster/topology-manager.md b/content/en/docs/tasks/administer-cluster/topology-manager.md
index 2d20619d84..76200482ca 100644
--- a/content/en/docs/tasks/administer-cluster/topology-manager.md
+++ b/content/en/docs/tasks/administer-cluster/topology-manager.md
@@ -211,14 +211,18 @@ that have the `Topology Affinity` error.
### Topology manager policy options
Support for the Topology Manager policy options requires `TopologyManagerPolicyOptions`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled.
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled
+(it is enabled by default).
You can toggle groups of options on and off based upon their maturity level using the following feature gates:
-* `TopologyManagerPolicyBetaOptions` default disabled. Enable to show beta-level options. Currently there are no beta-level options.
-* `TopologyManagerPolicyAlphaOptions` default disabled. Enable to show alpha-level options. You will still have to enable each option using the `TopologyManagerPolicyOptions` kubelet option.
+* `TopologyManagerPolicyBetaOptions` default enabled. Enable to show beta-level options.
+* `TopologyManagerPolicyAlphaOptions` default disabled. Enable to show alpha-level options.
+
+You will still have to enable each option using the `TopologyManagerPolicyOptions` kubelet option.
The following policy options exists:
-* `prefer-closest-numa-nodes` (alpha, invisible by default, `TopologyManagerPolicyOptions` and `TopologyManagerPolicyAlphaOptions` feature gates have to be enabled)(1.26 or higher)
+* `prefer-closest-numa-nodes` (beta, visible by default; `TopologyManagerPolicyOptions` and `TopologyManagerPolicyBetaOptions` feature gates have to be enabled).
+The `prefer-closest-numa-nodes` policy option is beta in Kubernetes {{< skew currentVersion >}}.
If the `prefer-closest-numa-nodes` policy option is specified, the `best-effort` and `restricted`
policies will favor sets of NUMA nodes with shorter distance between them when making admission decisions.
From 9af46c8913a360af15a547e6799f5bdfbb9e2e31 Mon Sep 17 00:00:00 2001
From: Evan Lezar
Date: Wed, 12 Jul 2023 22:10:34 +0200
Subject: [PATCH 063/446] Add CDI Devices to Device Plugin API
This change expands the documentation for the Device Plugin to include
the addition of support for CDI Device Names as a feature-gated feature
in the 1.28 release.
Signed-off-by: Evan Lezar
---
.../compute-storage-net/device-plugins.md | 16 ++++++++++++++++
1 file changed, 16 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 7722d9ffa8..f07ecc8fcb 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
@@ -147,6 +147,22 @@ The general workflow of a device plugin includes the following steps:
runtime configurations for accessing the allocated devices. The kubelet passes this information
to the container runtime.
+ An `AllocateResponse` contains zero or more `ContainerAllocateResponse` objects. In these, the
+ device plugin defines modifications that must be made to a container's definition to provide
+ access to the device. These modifications include:
+
+ * annotations
+ * device nodes
+ * environment variables
+ * mounts
+ * fully-qualified CDI device names
+
+ {{< note >}}
+ The processing of the fully-qualified CDI device names by the Device Manager requires
+ the `DevicePluginCDIDevices` feature gate to be enabled. This was added as an alpha feature in
+ v1.28.
+ {{< note >}}
+
### Handling kubelet restarts
A device plugin is expected to detect kubelet restarts and re-register itself with the new
From 6e1a413071c0a3bc302d4058269347fc2f56f043 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Mon, 24 Jul 2023 13:23:42 -0400
Subject: [PATCH 064/446] Update
content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2022-09-14-pod-has-network-condition.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
index b78d8dcf53..9eb0b940c0 100644
--- a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
+++ b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
@@ -25,7 +25,7 @@ repeatedly fail to come up.
### Updates for Kubernetes 1.28
-The PodHasNetwork condition has been renamed to PodReadyToStartContainers.
+The `PodHasNetwork` condition has been renamed to `PodReadyToStartContainers`.
To enable this alpha feature you have to set the feature toggle PodReadyToStartContainersCondition
to true.
From 20b50495e9c27760d99b2d7436eb89cbcb2d92e3 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Mon, 24 Jul 2023 13:23:58 -0400
Subject: [PATCH 065/446] Update
content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
Co-authored-by: Tim Bannister
---
.../en/blog/_posts/2022-09-14-pod-has-network-condition.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
index 9eb0b940c0..beb4b07c47 100644
--- a/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
+++ b/content/en/blog/_posts/2022-09-14-pod-has-network-condition.md
@@ -26,8 +26,9 @@ repeatedly fail to come up.
### Updates for Kubernetes 1.28
The `PodHasNetwork` condition has been renamed to `PodReadyToStartContainers`.
-To enable this alpha feature you have to set the feature toggle PodReadyToStartContainersCondition
-to true.
+Alongside that change, the feature gate `PodHasNetworkCondition` has been replaced by
+`PodReadyToStartContainersCondition`. You need to set `PodReadyToStartContainersCondition`
+to true in order to use the new feature in v1.28.0 and later.
### How is this different from the existing Initialized condition reported for pods?
From 7e208b05f1adb7873f3d6fe77dd08ff959e44095 Mon Sep 17 00:00:00 2001
From: Markus Lehtonen
Date: Mon, 24 Jul 2023 21:42:56 +0300
Subject: [PATCH 066/446] docs: incorporate review comments from sftim
Co-authored-by: Tim Bannister
---
.../feature-gates.md | 13 +++++----
.../container-runtimes.md | 27 ++++++++-----------
.../kubeadm/configure-cgroup-driver.md | 10 +++----
3 files changed, 23 insertions(+), 27 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 9d94802ae7..bd47a9cf0d 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
@@ -561,11 +561,14 @@ Each feature gate is designed for enabling/disabling a specific feature:
track of the finished Pods to count towards completion.
- `KMSv2`: Enables KMS v2 API for encryption at rest. See [Using a KMS Provider for data encryption](/docs/tasks/administer-cluster/kms-provider) for more details.
- `KubeletCgroupDriverFromCRI`: Enable detection of the kubelet cgroup driver
- configuration option from the CRI. This feature gate requires the user run a
- container runtime that supports the `RuntimeConfig` CRI call. If both CRI and
- Kubelet support this feature, the kubelet will ignore the cgroupDriver
- (--cgroup-driver) configuration option. If the container runtime doesn't
- support it, the kubelet will fallback to using its cgroupDriver option.
+ configuration option from the {{}}.
+ You can use this feature gate on nodes with a kubelet that supports the feature gate
+ and where there is a CRI container runtime that supports the `RuntimeConfig`
+ CRI call. If both CRI and kubelet support this feature, the kubelet ignores the
+ `cgroupDriver` configuration setting (or deprecated `--cgroup-driver` command
+ line argument). If you enable this feature gate and the container runtime
+ doesn't support it, the kubelet falls back to using the driver configured using
+ the `cgroupDriver` configuration setting.
See [Configuring a cgroup driver](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver)
for more details.
- `KubeletCredentialProviders`: Enable kubelet exec credential providers for
diff --git a/content/en/docs/setup/production-environment/container-runtimes.md b/content/en/docs/setup/production-environment/container-runtimes.md
index 8b50d18365..ce49a7347d 100644
--- a/content/en/docs/setup/production-environment/container-runtimes.md
+++ b/content/en/docs/setup/production-environment/container-runtimes.md
@@ -157,12 +157,11 @@ Starting with v1.22 and later, when creating a cluster with kubeadm, if the user
the `cgroupDriver` field under `KubeletConfiguration`, kubeadm defaults it to `systemd`.
{{< /note >}}
-{{< note >}}
-Starting with v1.28 and later, with KubeletCgroupDriverFromCRI feature gate
-enabled and a container runtime that supports the RuntimeConfig CRI rpc,
-kubelet will automatically detect the cgroup driver from the runtime and the
-cgroupDriver setting in kubelet configuration is ignored.
-{{< /note >}}
+For Kubernetes v1.28 and later, with the `KubeletCgroupDriverFromCRI`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+enabled and a container runtime that supports the `RuntimeConfig` CRI RPC,
+the kubelet automatically detects the appropriate cgroup driver from the runtime,
+and ignores the `cgroupDriver` setting within the kubelet configuration.
If you configure `systemd` as the cgroup driver for the kubelet, you must also
configure `systemd` as the cgroup driver for the container runtime. Refer to
@@ -258,11 +257,9 @@ sudo systemctl restart containerd
When using kubeadm, manually configure the
[cgroup driver for kubelet](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/#configuring-the-kubelet-cgroup-driver).
-{{< note >}}
-Starting with v1.28 and later, kubelet cgroup driver does not need to be
-configured if the KubeletCgroupDriverFromCRI feature gate is enabled and a
-version of containerd that supports the RuntimeConfig CRI rpc is being used.
-{{< /note >}}
+Starting with v1.28 and later, you can enable automatic detection of the
+cgroup driver as an alpha feature. See [systemd cgroup driver](#systemd-cgroup-driver)
+for more details.
#### Overriding the sandbox (pause) image {#override-pause-image-containerd}
@@ -305,11 +302,9 @@ You should also note the changed `conmon_cgroup`, which has to be set to the val
cgroup driver configuration of the kubelet (usually done via kubeadm) and CRI-O
in sync.
-{{< note >}}
-Starting with v1.28 and later, kubelet cgroup driver does not need to be
-configured if the KubeletCgroupDriverFromCRI feature gate is enabled and a
-version of CRI-O that supports the RuntimeConfig CRI rpc is being used.
-{{< /note >}}
+Starting with v1.28 and later, you can enable automatic detection of the
+cgroup driver as an alpha feature. See [systemd cgroup driver](#systemd-cgroup-driver)
+for more details.
For CRI-O, the CRI socket is `/var/run/crio/crio.sock` by default.
diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
index 9c65eb67a7..e3133054f5 100644
--- a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
+++ b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
@@ -36,13 +36,11 @@ driver of the kubelet.
{{< note >}}
In v1.22 and later, if the user does not set the `cgroupDriver` field under `KubeletConfiguration`,
kubeadm defaults it to `systemd`.
-{{< /note >}}
-{{< note >}}
-In v1.28 and later, with KubeletCgroupDriverFromCRI feature gate
-enabled and a container runtime that supports the RuntimeConfig CRI rpc,
-kubelet will automatically detect the cgroup driver from the runtime and the
-kubelet cgroup driver setting does not need to be manually configured.
+Starting with v1.28 and later, you can enable automatic detection of the
+cgroup driver as an alpha feature.
+See [systemd cgroup driver](/docs/setup/production-environment/container-runtimes/#systemd-cgroup-driver)
+for more details.
{{< /note >}}
A minimal example of configuring the field explicitly:
From 1c7f760100e94769e1a6b409d6c24e759cbfe19f Mon Sep 17 00:00:00 2001
From: Amine
Date: Mon, 24 Jul 2023 23:10:28 +0100
Subject: [PATCH 067/446] Graduate AdmissionWebhookMatchConditions 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 5aa6175027..2ae0634e0a 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 | |
-| `AdmissionWebhookMatchConditions` | `false` | Alpha | 1.27 | |
+| `AdmissionWebhookMatchConditions` | `false` | Alpha | 1.27 | 1.27 |
+| `AdmissionWebhookMatchConditions` | `true` | Beta | 1.28 | |
| `AggregatedDiscoveryEndpoint` | `false` | Alpha | 1.26 | 1.26 |
| `AggregatedDiscoveryEndpoint` | `true` | Beta | 1.27 | |
| `AnyVolumeDataSource` | `false` | Alpha | 1.18 | 1.23 |
From f9c824917fefcc98bc79e5556a11160c1048662e Mon Sep 17 00:00:00 2001
From: Amine
Date: Mon, 24 Jul 2023 23:10:55 +0100
Subject: [PATCH 068/446] convert the `ValidatingWebhookConfiguration` example
into a manifest using a codenew shortcode
---
.../extensible-admission-controllers.md | 52 +------------------
...ebhook-configuration-match-conditions.yaml | 47 +++++++++++++++++
2 files changed, 49 insertions(+), 50 deletions(-)
create mode 100644 content/en/examples/access/validating-webhook-configuration-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 9be36e8d11..b909bb131f 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
@@ -721,7 +721,7 @@ The `matchPolicy` for an admission webhooks defaults to `Equivalent`.
### Matching requests: `matchConditions`
-{{< feature-state state="alpha" for_k8s_version="v1.27" >}}
+{{< feature-state state="beta" for_k8s_version="v1.28" >}}
{{< note >}}
Use of `matchConditions` requires the [featuregate](/docs/reference/command-line-tools-reference/feature-gates/)
@@ -736,55 +736,7 @@ webhook to be called.
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' # Fail-open (optional)
- sideEffects: None
- clientConfig:
- service:
- namespace: my-namespace
- name: my-webhook
- caBundle: ''
- 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: ''
- 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()'
-```
+{{< codenew file="access/validating-webhook-configuration-match-conditions.yaml" >}}
Match conditions have access to the following CEL variables:
diff --git a/content/en/examples/access/validating-webhook-configuration-match-conditions.yaml b/content/en/examples/access/validating-webhook-configuration-match-conditions.yaml
new file mode 100644
index 0000000000..f9a3b25624
--- /dev/null
+++ b/content/en/examples/access/validating-webhook-configuration-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: ''
+ 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: ''
+ 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()'
\ No newline at end of file
From 7cf6eedd631911140c1596bc0e353557a18d73d9 Mon Sep 17 00:00:00 2001
From: Alexander Zielenski <351783+alexzielenski@users.noreply.github.com>
Date: Mon, 24 Jul 2023 18:28:45 -0700
Subject: [PATCH 069/446] add note about CRDValidationRatcheting feature gate
---
.../command-line-tools-reference/feature-gates.md | 13 +++++++++++++
1 file changed, 13 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 88e2cae5d5..18a74a2481 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
@@ -89,6 +89,7 @@ For a reference to old feature gates that are removed, please refer to
| `ComponentSLIs` | `true` | Beta | 1.27 | |
| `ContainerCheckpoint` | `false` | Alpha | 1.25 | |
| `ContextualLogging` | `false` | Alpha | 1.24 | |
+| CRDValidationRatcheting | false | Alpha | 1.28 |
| `CrossNamespaceVolumeDataSource` | `false` | Alpha| 1.26 | |
| `CustomCPUCFSQuotaPeriod` | `false` | Alpha | 1.12 | |
| `CustomResourceValidationExpressions` | `false` | Alpha | 1.23 | 1.24 |
@@ -457,6 +458,18 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `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/)
+- `CRDValidationRatcheting`: Enable updates to custom resources to contain
+ violations of their OpenAPI schema if the offending portions of the resource
+ update did not change. Allows users to update to stricter versions of a CRD
+ schema without bumping the version of the object or breaking workflows.
+ While most are supported, does not support ratcheting updates across all
+ schema changes. The following OpenAPIV3 schema validations are not supported
+ by ratcheting under the current implementation and if violated will continue
+ to throw an error as normally:
+ - `allOf`/`oneOf`/`anyOf`/`not` nested validations
+ - `x-kubernetes-validations`
+ - `x-kubernetes-list-type`
+ - `required` fields
- `CrossNamespaceVolumeDataSource`: Enable the usage of cross namespace volume data source
to allow you to specify a source namespace in the `dataSourceRef` field of a
PersistentVolumeClaim.
From 61d5b61ba52d7464258cdfdc392e4f6ec394a6a3 Mon Sep 17 00:00:00 2001
From: Cici Huang
Date: Tue, 25 Jul 2023 00:15:13 +0000
Subject: [PATCH 070/446] Address comments
---
.../custom-resource-definitions.md | 55 ++++++++++++++-----
1 file changed, 42 insertions(+), 13 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 bcf02cdb60..24d33985e6 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
@@ -1066,32 +1066,61 @@ 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.
-#### The reason and fieldPath fields
+Setting `messageExpression` is optional.
-Besides the `message` and `messageExpression` fields, which defines the string reported for a validation rule failure,
-we have also added two more fields under `validation`:
-- `reason` field which allows user to specify a machine-readable validation failure reason when a request fails this validation rule.
-- `fieldPath` field which specify the field path returned when the validation fails.
+#### The `message` field {#field-message}
+
+If you want to set a static message, you can supply `message` rather than `messageExpression`.
+The value of `message` is used as an opaque error string if validation fails.
+
+Setting `message` is optional.
+
+#### The `reason` field {#field-reason}
+
+You can add a machine-readable validation failure reason within a `validation`, to be returned
+whenever a request fails this validation rule.
For example:
```yaml
x-kubernetes-validations:
- rule: "self.x <= self.maxLimit"
- messageExpression: '"x exceeded max limit of " + string(self.maxLimit)'
reason: "FieldValueInvalid"
- fieldPath: ".x"
```
The HTTP status code returned to the caller will match the reason of the first failed validation rule.
The currently supported reasons are: "FieldValueInvalid", "FieldValueForbidden", "FieldValueRequired", "FieldValueDuplicate".
-If not set, default to use "FieldValueInvalid".
+If not set or unknown reasons, default to use "FieldValueInvalid".
-The `fieldPath` value must be a relative JSON path that is scoped to the location of this x-kubernetes-validations extension in the schema. Additionally, it should refer to an existing field within the schema.
-For example when validation checks if a specific attribute `foo` under a map `testMap`, the fieldPath could be set to `".testMap.foo"` or `.tetsMap['foo']'`.
-If the validation requires checking for unique attributes in two lists, the fieldPath can be set to either of the lists. For example, it can be set to `.testList1` or `.testList2`.
-It supports child operation to refer to an existing field currently. Refer to [JSONPath support in Kubernetes](https://kubernetes.io/docs/reference/kubectl/jsonpath/) for more info.
-And it does not support numeric index of array.
+Setting `reason` is optional.
+
+#### The `fieldPath` field {#field-field-path}
+
+You can specify the field path returned when the validation fails.
+
+For example:
+
+```yaml
+x-kubernetes-validations:
+- rule: "self.foo.test.x <= self.maxLimit"
+ fieldPath: ".foo.test.x"
+```
+
+In the example above, the validation checks the value of field `x` should be less than the value of `maxLimit`.
+If no `fieldPath` specified, when validation fails, the fieldPath would be default to wherever `self` scoped.
+With `fieldPath` specified, the returned error will have `fieldPath` properly refer to the location of field `x`.
+
+The `fieldPath` value must be a relative JSON path that is scoped to the location of this x-kubernetes-validations extension in the schema.
+Additionally, it should refer to an existing field within the schema.
+For example when validation checks if a specific attribute `foo` under a map `testMap`, you could set
+`fieldPath` to `".testMap.foo"` or `.testMap['foo']'`.
+If the validation requires checking for unique attributes in two lists, the fieldPath can be set to either of the lists.
+For example, it can be set to `.testList1` or `.testList2`.
+It supports child operation to refer to an existing field currently.
+Refer to [JSONPath support in Kubernetes](/docs/reference/kubectl/jsonpath/) for more info.
+The `fieldPath` field does not support indexing arrays numerically.
+
+Setting `fieldPath` is optional.
#### Validation functions {#available-validation-functions}
From 680148d71d84424966558785130d339a6696ff49 Mon Sep 17 00:00:00 2001
From: Marek Siarkowicz
Date: Wed, 19 Jul 2023 09:15:00 +0200
Subject: [PATCH 071/446] KEP-2340: Consistent Reads from Cache to Alpha
---
.../reference/command-line-tools-reference/feature-gates.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 88e2cae5d5..734d8ea0b7 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
@@ -87,6 +87,7 @@ For a reference to old feature gates that are removed, please refer to
| `ClusterTrustBundle` | false | Alpha | 1.27 | |
| `ComponentSLIs` | `false` | Alpha | 1.26 | 1.26 |
| `ComponentSLIs` | `true` | Beta | 1.27 | |
+ | `ConsistentListFromCache` | `false` | Alpha | 1.28 |
| `ContainerCheckpoint` | `false` | Alpha | 1.25 | |
| `ContextualLogging` | `false` | Alpha | 1.24 | |
| `CrossNamespaceVolumeDataSource` | `false` | Alpha| 1.26 | |
@@ -452,6 +453,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
allowing you to scrape health check metrics.
- `ConsistentHTTPGetHandlers`: Normalize HTTP get URL and Header passing for lifecycle
handlers with probers.
+- `ConsistentListFromCache`: Allow the API server to serve consistent lists from cache
- `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
From bf5eda7d3c0dc041f5716b4b6632c32a37a49f28 Mon Sep 17 00:00:00 2001
From: Andrey Goran
Date: Tue, 25 Jul 2023 12:31:42 +0400
Subject: [PATCH 072/446] FR localization: replaced {{< codenew ... >}} with
{{% codenew ... %}} in all files
---
.../concepts/cluster-administration/logging.md | 11 +++++------
.../concepts/services-networking/ingress.md | 2 +-
.../workloads/controllers/deployment.md | 2 +-
.../workloads/controllers/replicaset.md | 6 +++---
.../pods/pod-topology-spread-constraints.md | 6 +++---
.../docs/contribute/style/write-new-topic.md | 7 ++++---
.../docs/reference/access-authn-authz/rbac.md | 2 +-
.../connecting-frontend-backend.md | 10 +++++-----
.../service-access-application-cluster.md | 2 +-
.../running-cloud-controller.md | 2 +-
.../assign-cpu-resource.md | 4 ++--
.../assign-memory-resource.md | 6 +++---
.../assign-pods-nodes.md | 4 ++--
...figure-liveness-readiness-startup-probes.md | 6 +++---
.../configure-persistent-volume-storage.md | 8 ++++----
.../configure-pod-configmap.md | 18 +++++++++---------
.../configure-pod-initialization.md | 2 +-
.../configure-service-account.md | 2 +-
.../configure-volume-storage.md | 2 +-
.../extended-resource.md | 4 ++--
.../pull-image-private-registry.md | 2 +-
.../quality-service-pod.md | 8 ++++----
.../share-process-namespace.md | 2 +-
.../get-shell-running-container.md | 2 +-
.../define-command-argument-container.md | 2 +-
.../define-environment-variable-container.md | 2 +-
...ine-interdependent-environment-variables.md | 2 +-
.../distribute-credentials-secure.md | 10 +++++-----
...wnward-api-volume-expose-pod-information.md | 4 ++--
...ironment-variable-expose-pod-information.md | 4 ++--
.../horizontal-pod-autoscale-walkthrough.md | 6 ++++--
...run-single-instance-stateful-application.md | 4 ++--
.../run-stateless-application-deployment.md | 6 +++---
content/fr/docs/tutorials/hello-minikube.md | 4 ++--
34 files changed, 83 insertions(+), 81 deletions(-)
diff --git a/content/fr/docs/concepts/cluster-administration/logging.md b/content/fr/docs/concepts/cluster-administration/logging.md
index 0932de7406..52bcd88dff 100644
--- a/content/fr/docs/concepts/cluster-administration/logging.md
+++ b/content/fr/docs/concepts/cluster-administration/logging.md
@@ -50,7 +50,7 @@ d'évènements avec le flux de sortie standard. Cette démonstration utilise un
manifeste pour un Pod avec un seul conteneur qui écrit du texte sur le flux
de sortie standard toutes les secondes.
-{{< codenew file="debug/counter-pod.yaml" >}}
+{{% codenew file="debug/counter-pod.yaml" %}}
Pour lancer ce Pod, utilisez la commande suivante :
@@ -243,7 +243,7 @@ Un Pod exécute un unique conteneur et ce conteneur écrit dans deux fichiers de
journaux différents en utilisant deux format différents. Voici le manifeste du
Pod :
-{{< codenew file="admin/logging/two-files-counter-pod.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod.yaml" %}}
Il serait très désordonné d'avoir des évènements avec des formats différents
dans le même journal en redirigeant les évènements dans le flux de sortie
@@ -253,8 +253,7 @@ suit un des fichiers et renvoie les évènements sur son propre `stdout`.
Ci-dessous se trouve le manifeste pour un Pod avec deux conteneurs side-car.
-{{< codenew file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml"
->}}
+{{% codenew file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" %}}
Quand ce Pod s'exécute, chaque journal peut être diffusé séparément en
utilisant les commandes suivantes :
@@ -323,7 +322,7 @@ Le premier fichier contient un
[ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) pour
configurer fluentd.
-{{< codenew file="admin/logging/fluentd-sidecar-config.yaml" >}}
+{{% codenew file="admin/logging/fluentd-sidecar-config.yaml" %}}
{{< note >}}
La configuration de fluentd est hors du cadre de cet article. Vous trouverez
@@ -335,7 +334,7 @@ Le second fichier est un manifeste pour un Pod avec un conteneur side-car qui
exécute fluentd. Le Pod monte un volume où fluentd peut récupérer sa
configuration.
-{{< codenew file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" %}}
Apres quelques minutes, les évènements apparaîtront dans l'interface de
Stackdriver.
diff --git a/content/fr/docs/concepts/services-networking/ingress.md b/content/fr/docs/concepts/services-networking/ingress.md
index f7a1f0c240..140b15715d 100644
--- a/content/fr/docs/concepts/services-networking/ingress.md
+++ b/content/fr/docs/concepts/services-networking/ingress.md
@@ -330,7 +330,7 @@ type: kubernetes.io/tls
Référencer ce secret dans un Ingress indiquera au contrôleur d'Ingress de sécuriser le canal du client au load-balancer à l'aide de TLS. Vous devez vous assurer que le secret TLS que vous avez créé provenait d'un certificat contenant un Common Name (CN), aussi appelé nom de domaine pleinement qualifié (FQDN), pour `https-example.foo.com`.
-{{< codenew file="service/networking/tls-example-ingress.yaml" >}}
+{{% codenew file="service/networking/tls-example-ingress.yaml" %}}
{{< note >}}
diff --git a/content/fr/docs/concepts/workloads/controllers/deployment.md b/content/fr/docs/concepts/workloads/controllers/deployment.md
index d4df1e33b9..76d4c62cc6 100644
--- a/content/fr/docs/concepts/workloads/controllers/deployment.md
+++ b/content/fr/docs/concepts/workloads/controllers/deployment.md
@@ -49,7 +49,7 @@ Voici des cas d'utilisation typiques pour les déploiements:
Voici un exemple de déploiement.
Il crée un ReplicaSet pour faire apparaître trois pods `nginx`:
-{{< codenew file="controllers/nginx-deployment.yaml" >}}
+{{% codenew file="controllers/nginx-deployment.yaml" %}}
Dans cet exemple:
diff --git a/content/fr/docs/concepts/workloads/controllers/replicaset.md b/content/fr/docs/concepts/workloads/controllers/replicaset.md
index 3204d35277..9730600898 100644
--- a/content/fr/docs/concepts/workloads/controllers/replicaset.md
+++ b/content/fr/docs/concepts/workloads/controllers/replicaset.md
@@ -41,7 +41,7 @@ utilisez plutôt un déploiement et définissez votre application dans la sectio
## Exemple
-{{< codenew file="controllers/frontend.yaml" >}}
+{{% codenew file="controllers/frontend.yaml" %}}
Enregistrer ce manifeste dans `frontend.yaml` et le soumettre à un cluster Kubernetes va créer le ReplicaSet défini et les pods qu’il gère.
@@ -145,7 +145,7 @@ labels correspondant au sélecteur de l’un de vos ReplicaSets. Car un ReplicaS
Prenez l'exemple précédent de ReplicaSet, ainsi que les pods spécifiés dans le manifeste suivant :
-{{< codenew file="pods/pod-rs.yaml" >}}
+{{% codenew file="pods/pod-rs.yaml" %}}
Ces pods n’ayant pas de contrôleur (ni d’objet) en tant que référence propriétaire, ils correspondent au sélecteur de du ReplicaSet frontend, ils seront donc immédiatement acquis par ce ReplicaSet.
@@ -291,7 +291,7 @@ Un ReplicaSet peut également être une cible pour
Un ReplicaSet peut être mis à l'échelle automatiquement par un HPA. Voici un exemple HPA qui cible
le ReplicaSet que nous avons créé dans l'exemple précédent.
-{{< codenew file="controllers/hpa-rs.yaml" >}}
+{{% codenew file="controllers/hpa-rs.yaml" %}}
Enregistrer ce manifeste dans `hpa-rs.yaml` et le soumettre à un cluster Kubernetes devrait
créer le HPA défini qui scale automatiquement le ReplicaSet cible en fonction de l'utilisation du processeur
diff --git a/content/fr/docs/concepts/workloads/pods/pod-topology-spread-constraints.md b/content/fr/docs/concepts/workloads/pods/pod-topology-spread-constraints.md
index ea326f5c11..9fa8eec4a9 100644
--- a/content/fr/docs/concepts/workloads/pods/pod-topology-spread-constraints.md
+++ b/content/fr/docs/concepts/workloads/pods/pod-topology-spread-constraints.md
@@ -95,7 +95,7 @@ Supposons que vous ayez un cluster de 4 noeuds où 3 Pods étiquettés `foo:bar`
Si nous voulons qu'un nouveau Pod soit uniformément réparti avec les Pods existants à travers les zones, la spec peut être :
-{{< codenew file="pods/topology-spread-constraints/one-constraint.yaml" >}}
+{{% codenew file="pods/topology-spread-constraints/one-constraint.yaml" %}}
`topologyKey: zone` implique que la distribution uniforme sera uniquement appliquée pour les noeuds ayant le label "zone:<any value>" présent. `whenUnsatisfiable: DoNotSchedule` indique au scheduler de laisser le Pod dans l'état Pending si le Pod entrant ne peut pas satisfaire la contrainte.
@@ -133,7 +133,7 @@ Cela s'appuie sur l'exemple précédent. Supposons que vous ayez un cluster de 4
Vous pouvez utiliser 2 TopologySpreadConstraints pour contrôler la répartition des Pods aussi bien dans les zones que dans les noeuds :
-{{< codenew file="pods/topology-spread-constraints/two-constraints.yaml" >}}
+{{% codenew file="pods/topology-spread-constraints/two-constraints.yaml" %}}
Dans ce cas, pour satisfaire la première contrainte, le Pod entrant peut uniquement être placé dans "zoneB" ; alors que pour satisfaire la seconde contrainte, le Pod entrant peut uniquement être placé dans "node4". Le résultat étant l'intersection des résultats des 2 contraintes, l'unique option possible est de placer le Pod entrant dans "node4".
@@ -182,7 +182,7 @@ Il existe quelques conventions implicites qu'il est intéressant de noter ici :
et vous savez que "zoneC" doit être exclue. Dans ce cas, vous pouvez écrire le yaml ci-dessous, pour que "mypod" soit placé dans "zoneB" plutôt que dans "zoneC". `spec.nodeSelector` est pris en compte de la même manière.
- {{< codenew file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" >}}
+ {{% codenew file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" %}}
### Contraintes par défaut au niveau du cluster
diff --git a/content/fr/docs/contribute/style/write-new-topic.md b/content/fr/docs/contribute/style/write-new-topic.md
index 1027da53b6..d7780747dc 100644
--- a/content/fr/docs/contribute/style/write-new-topic.md
+++ b/content/fr/docs/contribute/style/write-new-topic.md
@@ -108,13 +108,14 @@ Utilisez cette méthode pour inclure des exemples de fichiers YAML lorsque l'éc
Lors de l'ajout d'un nouveau fichier d'exemple autonome, tel qu'un fichier YAML, placez le code dans l'un des sous-répertoires `/examples/` où `` est la langue utilisé dans votre page.
Dans votre fichier, utilisez le shortcode `codenew` :
-
{{< codenew file="<RELPATH>/my-example-yaml>" >}}
-
+```none
+{{%/* codenew file="/my-example-yaml>" */%}}
+```
où `` est le chemin vers le fichier à inclure, relatif au répertoire `examples`.
Le shortcode Hugo suivant fait référence à un fichier YAML situé sur `/content/en/examples/pods/storage/gce-volume.yaml`.
```none
-{{* codenew file="pods/storage/gce-volume.yaml" */>}}
+{{%/* codenew file="pods/storage/gce-volume.yaml" */%}}
```
{{< note >}}
diff --git a/content/fr/docs/reference/access-authn-authz/rbac.md b/content/fr/docs/reference/access-authn-authz/rbac.md
index afb0b266e5..be9206a015 100644
--- a/content/fr/docs/reference/access-authn-authz/rbac.md
+++ b/content/fr/docs/reference/access-authn-authz/rbac.md
@@ -1228,7 +1228,7 @@ comprend des recommandations pour restreindre cet accès dans les clusters exist
Si vous souhaitez que les nouveaux clusters conservent ce niveau d'accès dans les rôles agrégés,
vous pouvez créer le ClusterRole suivant :
-{{< codenew file="access/endpoints-aggregated.yaml" >}}
+{{% codenew file="access/endpoints-aggregated.yaml" %}}
## Mise à niveau à partir d'ABAC
diff --git a/content/fr/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/content/fr/docs/tasks/access-application-cluster/connecting-frontend-backend.md
index 1016696111..a3165ab992 100644
--- a/content/fr/docs/tasks/access-application-cluster/connecting-frontend-backend.md
+++ b/content/fr/docs/tasks/access-application-cluster/connecting-frontend-backend.md
@@ -33,7 +33,7 @@ Si votre environnement ne prend pas en charge cette fonction, vous pouvez utilis
Le backend est un simple microservice de salutations.
Voici le fichier de configuration pour le Deployment backend :
-{{< codenew file="service/access/backend-deployment.yaml" >}}
+{{% codenew file="service/access/backend-deployment.yaml" %}}
Créez le Deployment backend :
@@ -91,7 +91,7 @@ Un Service utilise des {{< glossary_tooltip text="sélecteurs" term_id="selector
Tout d'abord, explorez le fichier de configuration du Service :
-{{< codenew file="service/access/backend-service.yaml" >}}
+{{% codenew file="service/access/backend-service.yaml" %}}
Dans le fichier de configuration, vous pouvez voir que le Service,
nommé `hello`, achemine le trafic vers les Pods ayant les labels `app: hello` et `tier: backend`.
@@ -120,16 +120,16 @@ Les Pods du frontend Deployment exécutent une image nginx
configurée pour acheminer les requêtes vers le Service backend `hello`.
Voici le fichier de configuration nginx :
-{{< codenew file="service/access/frontend-nginx.conf" >}}
+{{% codenew file="service/access/frontend-nginx.conf" %}}
Comme pour le backend, le frontend dispose d'un Deployment et d'un Service.
Une différence importante à noter entre les services backend et frontend est que
le Service frontend est configuré avec un `type: LoadBalancer`, ce qui signifie que le Service utilise
un équilibreur de charge provisionné par votre fournisseur de cloud et sera accessible depuis l'extérieur du cluster.
-{{< codenew file="service/access/frontend-service.yaml" >}}
+{{% codenew file="service/access/frontend-service.yaml" %}}
-{{< codenew file="service/access/frontend-deployment.yaml" >}}
+{{% codenew file="service/access/frontend-deployment.yaml" %}}
Créez le Deployment et le Service frontend :
diff --git a/content/fr/docs/tasks/access-application-cluster/service-access-application-cluster.md b/content/fr/docs/tasks/access-application-cluster/service-access-application-cluster.md
index 4d15999ab3..b24d0b1da6 100644
--- a/content/fr/docs/tasks/access-application-cluster/service-access-application-cluster.md
+++ b/content/fr/docs/tasks/access-application-cluster/service-access-application-cluster.md
@@ -27,7 +27,7 @@ ayant deux instances en cours d'exécution.
Voici le fichier de configuration pour le déploiement de l'application :
-{{< codenew file="service/access/hello-application.yaml" >}}
+{{% codenew file="service/access/hello-application.yaml" %}}
1. Exécutez une application Hello World dans votre cluster :
Créez le déploiement de l'application en utilisant le fichier ci-dessus :
diff --git a/content/fr/docs/tasks/administer-cluster/running-cloud-controller.md b/content/fr/docs/tasks/administer-cluster/running-cloud-controller.md
index d2e9a02420..581a7043ad 100644
--- a/content/fr/docs/tasks/administer-cluster/running-cloud-controller.md
+++ b/content/fr/docs/tasks/administer-cluster/running-cloud-controller.md
@@ -74,7 +74,7 @@ Pour les cloud-controller-manager ne faisant pas partie de Kubernetes, vous pouv
Pour les fournisseurs qui se trouvent déjà dans Kubernetes, vous pouvez exécuter le cloud-controller-manager dans l'arborescence en tant que Daemonset dans votre cluster.
Utilisez ce qui suit comme guide:
-{{< codenew file="admin/cloud/ccm-example.yaml" >}}
+{{% codenew file="admin/cloud/ccm-example.yaml" %}}
## Limitations
diff --git a/content/fr/docs/tasks/configure-pod-container/assign-cpu-resource.md b/content/fr/docs/tasks/configure-pod-container/assign-cpu-resource.md
index 2d9af18838..8908405f09 100644
--- a/content/fr/docs/tasks/configure-pod-container/assign-cpu-resource.md
+++ b/content/fr/docs/tasks/configure-pod-container/assign-cpu-resource.md
@@ -64,7 +64,7 @@ dans le manifeste des ressources du conteneur. Pour spécifier une limite de CPU
Dans cet exercice, vous allez créer un Pod qui a un seul conteneur. Le conteneur a une demande de 0.5 CPU et une limite de 1 CPU. Voici le fichier de configuration du Pod :
-{{< codenew file="pods/resource/cpu-request-limit.yaml" >}}
+{{% codenew file="pods/resource/cpu-request-limit.yaml" %}}
La section `args` du fichier de configuration fournit des arguments pour le conteneur lorsqu'il démarre. L'argument `-cpus "2"` demande au conteneur d'utiliser 2 CPUs.
@@ -147,7 +147,7 @@ L'ordonnancement des pods est basé sur les demandes. Un Pod est prévu pour se
Dans cet exercice, vous allez créer un Pod qui a une demande de CPU si importante qu'elle dépassera la capacité de n'importe quel nœud de votre cluster. Voici le fichier de configuration d'un Pod
qui a un seul conteneur. Le conteneur nécessite 100 CPU, ce qui est susceptible de dépasser la capacité de tous les nœuds de votre cluster.
-{{< codenew file="pods/resource/cpu-request-limit-2.yaml" >}}
+{{% codenew file="pods/resource/cpu-request-limit-2.yaml" %}}
Créez le Pod :
diff --git a/content/fr/docs/tasks/configure-pod-container/assign-memory-resource.md b/content/fr/docs/tasks/configure-pod-container/assign-memory-resource.md
index 754e91972b..fce76eca88 100644
--- a/content/fr/docs/tasks/configure-pod-container/assign-memory-resource.md
+++ b/content/fr/docs/tasks/configure-pod-container/assign-memory-resource.md
@@ -60,7 +60,7 @@ dans le manifeste des ressources du conteneur. Pour spécifier une limite de mé
Dans cet exercice, vous créez un pod qui possède un seul conteneur. Le conteneur dispose d'une demande de mémoire de 100 MiB et une limite de mémoire de 200 MiB. Voici le fichier de configuration
pour le Pod :
-{{< codenew file="pods/resource/memory-request-limit.yaml" >}}
+{{% codenew file="pods/resource/memory-request-limit.yaml" %}}
La section `args` de votre fichier de configuration fournit des arguments pour le conteneur lorsqu'il démarre.
Les arguments `"--vm-bytes", "150M"` indiquent au conteneur d'allouer 150 MiB de mémoire.
@@ -123,7 +123,7 @@ Si un conteneur terminé peut être redémarré, le kubelet le redémarre, comme
Dans cet exercice, vous créez un Pod qui tente d'allouer plus de mémoire que sa limite.
Voici le fichier de configuration d'un Pod qui contient un conteneur avec une demande de mémoire de 50 MiB et une limite de mémoire de 100 MiB :
-{{< codenew file="pods/resource/memory-request-limit-2.yaml" >}}
+{{% codenew file="pods/resource/memory-request-limit-2.yaml" %}}
Dans la section `args` du fichier de configuration, vous pouvez voir que le conteneur
tentera d'allouer 250 MiB de mémoire, ce qui est bien au-dessus de la limite de 100 MiB.
@@ -226,7 +226,7 @@ L'ordonnancement des modules est basé sur les demandes. Un Pod est schedulé po
Dans cet exercice, vous allez créer un Pod dont la demande de mémoire est si importante qu'elle dépasse la capacité de la mémoire de n'importe quel nœud de votre cluster. Voici le fichier de configuration d'un Pod qui possède un seul conteneur avec une demande de 1000 GiB de mémoire, qui dépasse probablement la capacité de tous les nœuds de votre cluster.
-{{< codenew file="pods/resource/memory-request-limit-3.yaml" >}}
+{{% codenew file="pods/resource/memory-request-limit-3.yaml" %}}
Créez le Pod :
diff --git a/content/fr/docs/tasks/configure-pod-container/assign-pods-nodes.md b/content/fr/docs/tasks/configure-pod-container/assign-pods-nodes.md
index 3b102eee1f..be49ecd78b 100644
--- a/content/fr/docs/tasks/configure-pod-container/assign-pods-nodes.md
+++ b/content/fr/docs/tasks/configure-pod-container/assign-pods-nodes.md
@@ -62,7 +62,7 @@ Cette page montre comment assigner un Pod à un nœud particulier dans un cluste
Le fichier de configuration de pod décrit un pod qui possède un selector de nœud de type `disktype:ssd`. Cela signifie que le pod sera planifié sur un nœud ayant le label `disktype=ssd`.
-{{< codenew file="pods/pod-nginx.yaml" >}}
+{{% codenew file="pods/pod-nginx.yaml" %}}
1. Utilisez le fichier de configuration pour créer un pod qui sera ordonnancé sur votre nœud choisi :
@@ -86,7 +86,7 @@ Le fichier de configuration de pod décrit un pod qui possède un selector de n
Vous pouvez également ordonnancer un pod sur un nœud spécifique via le paramètre `nodeName`.
-{{< codenew file="pods/pod-nginx-specific-node.yaml" >}}
+{{% codenew file="pods/pod-nginx-specific-node.yaml" %}}
Utilisez le fichier de configuration pour créer un pod qui sera ordonnancé sur `foo-node` uniquement.
diff --git a/content/fr/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/fr/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index 39cf2ecbd4..3778d67924 100644
--- a/content/fr/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/fr/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -29,7 +29,7 @@ De nombreuses applications fonctionnant pour des longues périodes finissent par
Dans cet exercice, vous allez créer un Pod qui exécute un conteneur basé sur l'image `registry.k8s.io/busybox`. Voici le fichier de configuration pour le Pod :
-{{< codenew file="pods/probe/exec-liveness.yaml" >}}
+{{% codenew file="pods/probe/exec-liveness.yaml" %}}
Dans le fichier de configuration, vous constatez que le Pod a un seul conteneur.
Le champ `periodSeconds` spécifie que le Kubelet doit effectuer un check de liveness toutes les 5 secondes. Le champ `initialDelaySeconds` indique au Kubelet qu'il devrait attendre 5 secondes avant d'effectuer la première probe. Pour effectuer une probe, le Kubelet exécute la commande `cat /tmp/healthy` dans le conteneur. Si la commande réussit, elle renvoie 0, et le Kubelet considère que le conteneur est vivant et en bonne santé. Si la commande renvoie une valeur non nulle, le Kubelet tue le conteneur et le redémarre.
@@ -104,7 +104,7 @@ liveness-exec 1/1 Running 1 1m
Un autre type de liveness probe utilise une requête GET HTTP. Voici la configuration
d'un Pod qui fait fonctionner un conteneur basé sur l'image `registry.k8s.io/liveness`.
-{{< codenew file="pods/probe/http-liveness.yaml" >}}
+{{% codenew file="pods/probe/http-liveness.yaml" %}}
Dans le fichier de configuration, vous pouvez voir que le Pod a un seul conteneur.
Le champ `periodSeconds` spécifie que le Kubelet doit effectuer une liveness probe toutes les 3 secondes. Le champ `initialDelaySeconds` indique au Kubelet qu'il devrait attendre 3 secondes avant d'effectuer la première probe. Pour effectuer une probe, le Kubelet envoie une requête HTTP GET au serveur qui s'exécute dans le conteneur et écoute sur le port 8080. Si le handler du chemin `/healthz` du serveur renvoie un code de succès, le Kubelet considère que le conteneur est vivant et en bonne santé. Si le handler renvoie un code d'erreur, le Kubelet tue le conteneur et le redémarre.
@@ -152,7 +152,7 @@ Dans les versions postérieures à la v1.13, les paramètres de la variable d'en
Un troisième type de liveness probe utilise un TCP Socket. Avec cette configuration, le Kubelet tentera d'ouvrir un socket vers votre conteneur sur le port spécifié.
S'il arrive à établir une connexion, le conteneur est considéré comme étant en bonne santé, s'il n'y arrive pas, c'est un échec.
-{{< codenew file="pods/probe/tcp-liveness-readiness.yaml" >}}
+{{% codenew file="pods/probe/tcp-liveness-readiness.yaml" %}}
Comme vous le voyez, la configuration pour un check TCP est assez similaire à un check HTTP.
Cet exemple utilise à la fois des readiness et liveness probes. Le Kubelet transmettra la première readiness probe 5 secondes après le démarrage du conteneur. Il tentera de se connecter au conteneur `goproxy` sur le port 8080. Si la probe réussit, le conteneur sera marqué comme prêt. Kubelet continuera à effectuer ce check tous les 10 secondes.
diff --git a/content/fr/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md b/content/fr/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md
index 75ae3c6846..4f4ae7fca4 100644
--- a/content/fr/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md
+++ b/content/fr/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md
@@ -75,7 +75,7 @@ pour paramétrer du
[provisioning dynamique](/docs/concepts/storage/dynamic-provisioning/).
Voici le fichier de configuration pour le PersistentVolume de type hostPath:
-{{< codenew file="pods/storage/pv-volume.yaml" >}}
+{{% codenew file="pods/storage/pv-volume.yaml" %}}
Le fichier de configuration spécifie que le chemin du volume sur le noeud est `/mnt/data`. Il spécifie aussi une taille de 10 gibibytes, ainsi qu'un mode d'accès de type `ReadWriteOnce`, impliquant que le volume ne peut être monté en lecture et écriture que par un seul noeud. Le fichier définit un [nom de StorageClass](/docs/concepts/storage/persistent-volumes/#class) à `manual`, ce qui sera utilisé pour attacher un PersistentVolumeClaim à ce PersistentVolume
@@ -103,7 +103,7 @@ La prochaine étape est de créer un PersistentVolumeClaim (demande de stockage)
Dans cet exercice, vous créez un PersistentVolumeClaim qui demande un volume d'au moins 3 GB, et qui peut être monté en lecture et écriture sur au moins un noeud.
Voici le fichier de configuration du PersistentVolumeClaim:
-{{< codenew file="pods/storage/pv-claim.yaml" >}}
+{{% codenew file="pods/storage/pv-claim.yaml" %}}
Créez le PersistentVolumeClaim:
@@ -137,7 +137,7 @@ La prochaine étape est de créer un Pod qui utilise le PersistentVolumeClaim co
Voici le fichier de configuration du Pod:
-{{< codenew file="pods/storage/pv-pod.yaml" >}}
+{{% codenew file="pods/storage/pv-pod.yaml" %}}
Notez que le fichier de configuration du Pod spécifie un PersistentVolumeClaim et non un PersistentVolume. Du point de vue du Pod, la demande est un volume de stockage.
@@ -200,7 +200,7 @@ Vous pouvez maintenant arrêter la session shell vers votre noeud.
Vous pouvez monter plusieurs fois un même PersistentVolume
à plusieurs endroits différents dans votre container nginx:
-{{< codenew file="pods/storage/pv-duplicate.yaml" >}}
+{{% codenew file="pods/storage/pv-duplicate.yaml" %}}
- `/usr/share/nginx/html` pour le site statique
- `/etc/nginx/nginx.conf` pour la configuration par défaut
diff --git a/content/fr/docs/tasks/configure-pod-container/configure-pod-configmap.md b/content/fr/docs/tasks/configure-pod-container/configure-pod-configmap.md
index 6e9c4c5ba6..6fa439bdad 100644
--- a/content/fr/docs/tasks/configure-pod-container/configure-pod-configmap.md
+++ b/content/fr/docs/tasks/configure-pod-container/configure-pod-configmap.md
@@ -453,7 +453,7 @@ configmap/special-config-2-c92b5mmcf2 created
1. Attribuez la valeur `special.how` défini dans ConfigMap à la variable d'environnement `SPECIAL_LEVEL_KEY` dans la spécification du Pod.
- {{< codenew file="pods/pod-single-configmap-env-variable.yaml" >}}
+ {{% codenew file="pods/pod-single-configmap-env-variable.yaml" %}}
Créez le pod:
@@ -467,7 +467,7 @@ configmap/special-config-2-c92b5mmcf2 created
* Comme avec l'exemple précédent, créez d'abord les ConfigMaps.
- {{< codenew file="configmap/configmaps.yaml" >}}
+ {{% codenew file="configmap/configmaps.yaml" %}}
Créez le ConfigMap:
@@ -477,7 +477,7 @@ configmap/special-config-2-c92b5mmcf2 created
* Définissez les variables d'environnement dans la spécification Pod.
- {{< codenew file="pods/pod-multiple-configmap-env-variable.yaml" >}}
+ {{% codenew file="pods/pod-multiple-configmap-env-variable.yaml" %}}
Créez le pod:
@@ -495,7 +495,7 @@ Cette fonctionnalité est disponible dans Kubernetes v1.6 et versions ultérieur
* Créez un ConfigMap contenant plusieurs paires clé-valeur.
- {{< codenew file="configmap/configmap-multikeys.yaml" >}}
+ {{% codenew file="configmap/configmap-multikeys.yaml" %}}
Créez le ConfigMap:
@@ -506,7 +506,7 @@ Cette fonctionnalité est disponible dans Kubernetes v1.6 et versions ultérieur
* Utilisez `envFrom` pour définir toutes les données du ConfigMap en tant que variables d'environnement du conteneur.
La clé de ConfigMap devient le nom de la variable d'environnement dans le pod.
- {{< codenew file="pods/pod-configmap-envFrom.yaml" >}}
+ {{% codenew file="pods/pod-configmap-envFrom.yaml" %}}
Créez le pod:
@@ -522,7 +522,7 @@ Vous pouvez utiliser des variables d'environnement définies par ConfigMap dans
Par exemple, la spécification de pod suivante
-{{< codenew file="pods/pod-configmap-env-var-valueFrom.yaml" >}}
+{{% codenew file="pods/pod-configmap-env-var-valueFrom.yaml" %}}
créé en exécutant
@@ -543,7 +543,7 @@ Le contenu du fichier devient la valeur de la clé.
Les exemples de cette section se réfèrent à un ConfigMap nommé special-config, illustré ci-dessous.
-{{< codenew file="configmap/configmap-multikeys.yaml" >}}
+{{% codenew file="configmap/configmap-multikeys.yaml" %}}
Créez le ConfigMap:
@@ -557,7 +557,7 @@ Ajoutez le nom ConfigMap sous la section `volumes` de la spécification Pod.
Ceci ajoute les données ConfigMap au répertoire spécifié comme `volumeMounts.mountPath` (dans ce cas, `/etc/config`).
La section `command` répertorie les fichiers de répertoire dont les noms correspondent aux clés de ConfigMap.
-{{< codenew file="pods/pod-configmap-volume.yaml" >}}
+{{% codenew file="pods/pod-configmap-volume.yaml" %}}
Créez le pod:
@@ -581,7 +581,7 @@ S'il y a des fichiers dans le dossier `/etc/config/`, ils seront supprimés.
Utilisez le champ `path` pour spécifier le chemin de fichier souhaité pour les éléments de configmap spécifiques.
Dans ce cas, le `SPECIAL_LEVEL` sera monté dans le volume `config-volume` au chemin `/etc/config/keys`.
-{{< codenew file="pods/pod-configmap-volume-specific-key.yaml" >}}
+{{% codenew file="pods/pod-configmap-volume-specific-key.yaml" %}}
Créez le Pod :
diff --git a/content/fr/docs/tasks/configure-pod-container/configure-pod-initialization.md b/content/fr/docs/tasks/configure-pod-container/configure-pod-initialization.md
index eeb33a0d4b..7017ecbd68 100644
--- a/content/fr/docs/tasks/configure-pod-container/configure-pod-initialization.md
+++ b/content/fr/docs/tasks/configure-pod-container/configure-pod-initialization.md
@@ -24,7 +24,7 @@ Dans cet exercice, vous allez créer un Pod qui a un conteneur d'application et
Voici le fichier de configuration du Pod :
-{{< codenew file="pods/init-containers.yaml" >}}
+{{% codenew file="pods/init-containers.yaml" %}}
Dans le fichier de configuration, vous pouvez voir que le Pod a un Volume que le conteneur d'initialisation et le conteneur d'application partagent.
diff --git a/content/fr/docs/tasks/configure-pod-container/configure-service-account.md b/content/fr/docs/tasks/configure-pod-container/configure-service-account.md
index 4f38f3a397..f3b862a684 100644
--- a/content/fr/docs/tasks/configure-pod-container/configure-service-account.md
+++ b/content/fr/docs/tasks/configure-pod-container/configure-service-account.md
@@ -269,7 +269,7 @@ Ce comportement est configuré sur un PodSpec utilisant un type de ProjectedVolu
[ServiceAccountToken](/docs/concepts/storage/volumes/#projected). Pour fournir un
Pod avec un token avec une audience de "vault" et une durée de validité de deux heures, vous devriez configurer ce qui suit dans votre PodSpec :
-{{< codenew file="pods/pod-projected-svc-token.yaml" >}}
+{{% codenew file="pods/pod-projected-svc-token.yaml" %}}
Créez le Pod
diff --git a/content/fr/docs/tasks/configure-pod-container/configure-volume-storage.md b/content/fr/docs/tasks/configure-pod-container/configure-volume-storage.md
index 3c17aa3cda..7fdb1e4a54 100644
--- a/content/fr/docs/tasks/configure-pod-container/configure-volume-storage.md
+++ b/content/fr/docs/tasks/configure-pod-container/configure-volume-storage.md
@@ -29,7 +29,7 @@ Dans cet exercice, vous créez un pod qui contient un seul conteneur. Ce Pod a u
[emptyDir](/fr/docs/concepts/storage/volumes/#emptydir) qui dure toute la vie du Pod, même si le conteneur se termine et redémarre.
Voici le fichier de configuration du Pod :
-{{< codenew file="pods/storage/redis.yaml" >}}
+{{% codenew file="pods/storage/redis.yaml" %}}
1. Créez le Pod :
diff --git a/content/fr/docs/tasks/configure-pod-container/extended-resource.md b/content/fr/docs/tasks/configure-pod-container/extended-resource.md
index 439714f6fd..68a79a6073 100644
--- a/content/fr/docs/tasks/configure-pod-container/extended-resource.md
+++ b/content/fr/docs/tasks/configure-pod-container/extended-resource.md
@@ -34,7 +34,7 @@ Les noms de ressources supplémentaires valides ont la forme `example.com/foo` o
Voici le fichier de configuration d'un Pod qui a un seul conteneur :
-{{< codenew file="pods/resource/extended-resource-pod.yaml" >}}
+{{% codenew file="pods/resource/extended-resource-pod.yaml" %}}
Dans le fichier de configuration, vous pouvez constater que le conteneur demande 3 dongles.
@@ -70,7 +70,7 @@ Requests:
Voici le fichier de configuration d'un Pod qui a un seul conteneur. Le conteneur demande
deux dongles.
-{{< codenew file="pods/resource/extended-resource-pod-2.yaml" >}}
+{{% codenew file="pods/resource/extended-resource-pod-2.yaml" %}}
Kubernetes ne pourra pas satisfaire la demande de deux dongles, parce que le premier Pod
a utilisé trois des quatre dongles disponibles.
diff --git a/content/fr/docs/tasks/configure-pod-container/pull-image-private-registry.md b/content/fr/docs/tasks/configure-pod-container/pull-image-private-registry.md
index efe9ee74fa..c4917e5a21 100644
--- a/content/fr/docs/tasks/configure-pod-container/pull-image-private-registry.md
+++ b/content/fr/docs/tasks/configure-pod-container/pull-image-private-registry.md
@@ -170,7 +170,7 @@ Vous avez réussi à définir vos identifiants de Docker comme un Secret appelé
Voici un fichier de configuration pour un Pod qui a besoin d'accéder à vos identifiants Docker dans `regcred` :
-{{< codenew file="pods/private-reg-pod.yaml" >}}
+{{% codenew file="pods/private-reg-pod.yaml" %}}
Téléchargez le fichier ci-dessus :
diff --git a/content/fr/docs/tasks/configure-pod-container/quality-service-pod.md b/content/fr/docs/tasks/configure-pod-container/quality-service-pod.md
index 93e785f54c..a8056b94a4 100644
--- a/content/fr/docs/tasks/configure-pod-container/quality-service-pod.md
+++ b/content/fr/docs/tasks/configure-pod-container/quality-service-pod.md
@@ -48,7 +48,7 @@ Pour qu'un Pod reçoive une classe de QoS Guaranteed :
Ci-dessous le fichier de configuration d'un Pod qui a un seul conteneur.
Le conteneur dispose d'une limite de mémoire et d'une demande de mémoire, tous deux égaux à 200 MiB. Le conteneur a également une limite CPU et une demande CPU, toutes deux égales à 700 milliCPU :
-{{< codenew file="pods/qos/qos-pod.yaml" >}}
+{{% codenew file="pods/qos/qos-pod.yaml" %}}
Créez le Pod :
@@ -99,7 +99,7 @@ Un Pod reçoit une classe QoS de Burstable si :
Voici le fichier de configuration d'un pod qui a un seul conteneur. Le conteneur a une limite de mémoire de 200 MiB et une demande de mémoire de 100 MiB.
-{{< codenew file="pods/qos/qos-pod-2.yaml" >}}
+{{% codenew file="pods/qos/qos-pod-2.yaml" %}}
Créez le Pod :
@@ -143,7 +143,7 @@ avoir des limites ou des demandes de mémoire ou de CPU.
Voici le fichier de configuration d'un Pod qui a un seul conteneur. Le conteneur n'a pas des limites ou des demandes de mémoire ou de CPU :
-{{< codenew file="pods/qos/qos-pod-3.yaml" >}}
+{{% codenew file="pods/qos/qos-pod-3.yaml" %}}
Créez le Pod :
@@ -181,7 +181,7 @@ kubectl delete pod qos-demo-3 --namespace=qos-example
Voici le fichier de configuration d'un Pod qui a deux conteneurs. Un conteneur spécifie une
demande de mémoire de 200 MiB. L'autre conteneur ne spécifie aucune demande ou limite.
-{{< codenew file="pods/qos/qos-pod-4.yaml" >}}
+{{% codenew file="pods/qos/qos-pod-4.yaml" %}}
Notez que le pod répond aux critères de la classe QoS Burstable. En d'autres termes, il ne répond pas aux exigences de la classe de qualité de service Guaranteed, et l'un de ses conteneurs dispose d'une demande de mémoire.
diff --git a/content/fr/docs/tasks/configure-pod-container/share-process-namespace.md b/content/fr/docs/tasks/configure-pod-container/share-process-namespace.md
index cb5a99cbe3..5223490c6d 100644
--- a/content/fr/docs/tasks/configure-pod-container/share-process-namespace.md
+++ b/content/fr/docs/tasks/configure-pod-container/share-process-namespace.md
@@ -23,7 +23,7 @@ Vous pouvez utiliser cette fonctionnalité pour configurer les conteneurs coopé
Le partage de l'espace de nommage du processus est activé en utilisant le champ `shareProcessNamespace` de `v1.PodSpec`. Par exemple:
-{{< codenew file="pods/share-process-namespace.yaml" >}}
+{{% codenew file="pods/share-process-namespace.yaml" %}}
1. Créez le pod `nginx` sur votre cluster :
diff --git a/content/fr/docs/tasks/debug-application-cluster/get-shell-running-container.md b/content/fr/docs/tasks/debug-application-cluster/get-shell-running-container.md
index b5fb0012a1..1973bcd1bb 100644
--- a/content/fr/docs/tasks/debug-application-cluster/get-shell-running-container.md
+++ b/content/fr/docs/tasks/debug-application-cluster/get-shell-running-container.md
@@ -24,7 +24,7 @@ Dans cet exercice, vous allez créer un pod contenant un conteneur.
Le conteneur exécute une image nginx.
Voici le fichier de configuration du Pod:
-{{< codenew file="application/shell-demo.yaml" >}}
+{{% codenew file="application/shell-demo.yaml" %}}
Créez le Pod:
diff --git a/content/fr/docs/tasks/inject-data-application/define-command-argument-container.md b/content/fr/docs/tasks/inject-data-application/define-command-argument-container.md
index bf55910e44..b36ad83d15 100644
--- a/content/fr/docs/tasks/inject-data-application/define-command-argument-container.md
+++ b/content/fr/docs/tasks/inject-data-application/define-command-argument-container.md
@@ -38,7 +38,7 @@ Le champ `command` correspond à `entrypoint` dans certains runtimes de containe
Dans cet exercice, vous allez créer un Pod qui exécute un container.
Le fichier de configuration pour le Pod défini une commande ainsi que deux arguments:
-{{< codenew file="pods/commands.yaml" >}}
+{{% codenew file="pods/commands.yaml" %}}
1. Créez un Pod en utilisant le fichier YAML de configuration suivant:
diff --git a/content/fr/docs/tasks/inject-data-application/define-environment-variable-container.md b/content/fr/docs/tasks/inject-data-application/define-environment-variable-container.md
index c55aa45ac5..357b1da5f0 100644
--- a/content/fr/docs/tasks/inject-data-application/define-environment-variable-container.md
+++ b/content/fr/docs/tasks/inject-data-application/define-environment-variable-container.md
@@ -24,7 +24,7 @@ dans le fichier de configuration.
Dans cet exercice, vous allez créer un Pod qui exécute un container. Le fichier de configuration pour ce Pod contient une variable d'environnement s'appelant `DEMO_GREETING` et sa valeur est `"Hello from the environment"`. Voici le fichier de configuration du Pod:
-{{< codenew file="pods/inject/envars.yaml" >}}
+{{% codenew file="pods/inject/envars.yaml" %}}
1. Créez un Pod à partir de ce fichier:
diff --git a/content/fr/docs/tasks/inject-data-application/define-interdependent-environment-variables.md b/content/fr/docs/tasks/inject-data-application/define-interdependent-environment-variables.md
index 73bf9afa94..b532e6e40e 100644
--- a/content/fr/docs/tasks/inject-data-application/define-interdependent-environment-variables.md
+++ b/content/fr/docs/tasks/inject-data-application/define-interdependent-environment-variables.md
@@ -25,7 +25,7 @@ Pour définir une variable d'environnement dépendante, vous pouvez utiliser le
Dans cette exercice, vous allez créer un Pod qui exécute un container. Le fichier de configuration de ce Pod définit des variables d'environnement interdépendantes avec une ré-utilisation entre les différentes variables. Voici le fichier de configuration de ce Pod:
-{{< codenew file="pods/inject/dependent-envars.yaml" >}}
+{{% codenew file="pods/inject/dependent-envars.yaml" %}}
1. Créez un Pod en utilisant ce fichier de configuration:
diff --git a/content/fr/docs/tasks/inject-data-application/distribute-credentials-secure.md b/content/fr/docs/tasks/inject-data-application/distribute-credentials-secure.md
index f2052c52ff..2faf3caa83 100644
--- a/content/fr/docs/tasks/inject-data-application/distribute-credentials-secure.md
+++ b/content/fr/docs/tasks/inject-data-application/distribute-credentials-secure.md
@@ -39,7 +39,7 @@ afin de réduire les risques de sécurité liés à l'utilisation d'un outil ext
Voici un fichier de configuration que vous pouvez utiliser pour créer un Secret
qui contiendra votre identifiant et mot de passe:
-{{< codenew file="pods/inject/secret.yaml" >}}
+{{% codenew file="pods/inject/secret.yaml" %}}
1. Créez le Secret:
@@ -99,7 +99,7 @@ montrée précédemment permet de démontrer et comprendre le fonctionnement des
Voici un fichier de configuration qui permet de créer un Pod:
-{{< codenew file="pods/inject/secret-pod.yaml" >}}
+{{% codenew file="pods/inject/secret-pod.yaml" %}}
1. Créez le Pod:
@@ -255,7 +255,7 @@ permettant de redémarrer les containers lors d'une mise à jour du Secret.
* Assignez la valeur de `backend-username` définie dans le Secret
à la variable d'environnement `SECRET_USERNAME` dans la configuration du Pod.
- {{< codenew file="pods/inject/pod-single-secret-env-variable.yaml" >}}
+ {{% codenew file="pods/inject/pod-single-secret-env-variable.yaml" %}}
* Créez le Pod:
@@ -286,7 +286,7 @@ permettant de redémarrer les containers lors d'une mise à jour du Secret.
* Définissez les variables d'environnement dans la configuration du Pod.
- {{< codenew file="pods/inject/pod-multiple-secret-env-variable.yaml" >}}
+ {{% codenew file="pods/inject/pod-multiple-secret-env-variable.yaml" %}}
* Créez le Pod:
@@ -323,7 +323,7 @@ Cette fonctionnalité n'est disponible que dans les versions de Kubernetes
d'environnement. Les clés du Secret deviendront les noms des variables
d'environnement à l'intérieur du Pod.
- {{< codenew file="pods/inject/pod-secret-envFrom.yaml" >}}
+ {{% codenew file="pods/inject/pod-secret-envFrom.yaml" %}}
* Créez le Pod:
diff --git a/content/fr/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md b/content/fr/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md
index 764a0c24de..02e3cc332f 100644
--- a/content/fr/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md
+++ b/content/fr/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md
@@ -35,7 +35,7 @@ et vous allez projeter les champs d'informations du Pod à l'intérieur du
container via des fichiers dans le container.
Voici le fichier de configuration du Pod:
-{{< codenew file="pods/inject/dapi-volume.yaml" >}}
+{{% codenew file="pods/inject/dapi-volume.yaml" %}}
Dans la configuration, on peut voir que le Pod a un volume de type `downward API`, et que le container monte ce volume sur le chemin `/etc/podinfo`.
@@ -154,7 +154,7 @@ qui appartiennent au
[container](/docs/reference/kubernetes-api/workload-resources/pod-v1/#Container), plutôt qu'au Pod.
Voici un fichier de configuration pour un Pod qui n'a qu'un seul container:
-{{< codenew file="pods/inject/dapi-volume-resources.yaml" >}}
+{{% codenew file="pods/inject/dapi-volume-resources.yaml" %}}
Dans cette configuration, on peut voir que le Pod a un volume de type
[`downwardAPI`](/docs/concepts/storage/volumes/#downwardapi),
diff --git a/content/fr/docs/tasks/inject-data-application/environment-variable-expose-pod-information.md b/content/fr/docs/tasks/inject-data-application/environment-variable-expose-pod-information.md
index 06999676da..a44ce95370 100644
--- a/content/fr/docs/tasks/inject-data-application/environment-variable-expose-pod-information.md
+++ b/content/fr/docs/tasks/inject-data-application/environment-variable-expose-pod-information.md
@@ -32,7 +32,7 @@ Dans cette partie de l'exercice, vous allez créer un Pod qui a un container,
et vous allez projeter les champs d'informations du Pod à l'intérieur du
container comme variables d'environnement.
-{{< codenew file="pods/inject/dapi-envars-pod.yaml" >}}
+{{% codenew file="pods/inject/dapi-envars-pod.yaml" %}}
Dans ce fichier de configuration, on trouve cinq variables d'environnement.
Le champ `env` est une liste de variables d'environnement.
@@ -113,7 +113,7 @@ qui est exécuté à l'intérieur du Pod.
Voici un fichier de configuration pour un autre Pod qui ne contient qu'un seul
container:
-{{< codenew file="pods/inject/dapi-envars-container.yaml" >}}
+{{% codenew file="pods/inject/dapi-envars-container.yaml" %}}
Dans ce fichier, vous pouvez voir 4 variables d'environnement.
Le champ `env` est une liste de variables d'environnement.
diff --git a/content/fr/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/content/fr/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
index 4d686301c9..77b3741eaf 100644
--- a/content/fr/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+++ b/content/fr/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
@@ -53,7 +53,9 @@ Pour apprendre comment déployer le Metrics Server, consultez la [documentation
Pour démontrer un HorizontalPodAutoscaler, vous commencerez par démarrer un
Deployment qui exécute un conteneur utilisant l'image `hpa-example`
et l'expose en tant que {{< glossary_tooltip term_id="service">}} en utilisant le
-manifeste suivant: {{< codenew file="application/php-apache.yaml" >}}
+manifeste suivant:
+
+{{% codenew file="application/php-apache.yaml" %}}
Pour créer les ressources, exécutez la commande suivante:
```shell
@@ -505,7 +507,7 @@ Cela signifie que vous pouvez voir la valeur de votre métrique fluctuer entre `
Au lieu d'utiliser la commande `kubectl autoscale` pour créer un HorizontalPodAutoscaler de manière impérative,
nous pouvons utiliser le manifeste suivant pour le créer de manière déclarative :
-{{< codenew file=application/hpa/php-apache.yaml >}}
+{{% codenew file=application/hpa/php-apache.yaml %}}
Ensuite, créez l'autoscaler en exécutant la commande suivante :
diff --git a/content/fr/docs/tasks/run-application/run-single-instance-stateful-application.md b/content/fr/docs/tasks/run-application/run-single-instance-stateful-application.md
index d9d99be845..5ee3ebbfe7 100644
--- a/content/fr/docs/tasks/run-application/run-single-instance-stateful-application.md
+++ b/content/fr/docs/tasks/run-application/run-single-instance-stateful-application.md
@@ -37,8 +37,8 @@ Remarque: le mot de passe MySQL est défini dans le fichier de configuration YAM
Voir les [secrets Kubernetes](/docs/concepts/configuration/secret/)
pour une approche sécurisée.
-{{< codenew file="application/mysql/mysql-deployment.yaml" >}}
-{{< codenew file="application/mysql/mysql-pv.yaml" >}}
+{{% codenew file="application/mysql/mysql-deployment.yaml" %}}
+{{% codenew file="application/mysql/mysql-pv.yaml" %}}
1. Déployez le PV et le PVC du fichier YAML:
diff --git a/content/fr/docs/tasks/run-application/run-stateless-application-deployment.md b/content/fr/docs/tasks/run-application/run-stateless-application-deployment.md
index cb932a24cd..9e5d24ee47 100644
--- a/content/fr/docs/tasks/run-application/run-stateless-application-deployment.md
+++ b/content/fr/docs/tasks/run-application/run-stateless-application-deployment.md
@@ -28,7 +28,7 @@ déploiement Kubernetes, et vous pouvez décrire un
déploiement dans un fichier YAML. Par exemple,
ce fichier YAML décrit un déploiement qui exécute l'image Docker nginx:1.14.2 :
-{{< codenew file="application/deployment.yaml" >}}
+{{% codenew file="application/deployment.yaml" %}}
1. Créez un déploiement basé sur ce fichier YAML:
@@ -102,7 +102,7 @@ Vous pouvez mettre à jour le déploiement en appliquant un nouveau fichier YAML
Ce fichier YAML indique que le déploiement doit être mis à jour
pour utiliser nginx 1.16.1.
-{{< codenew file="application/deployment-update.yaml" >}}
+{{% codenew file="application/deployment-update.yaml" %}}
1. Appliquez le nouveau fichier YAML :
@@ -121,7 +121,7 @@ pour utiliser nginx 1.16.1.
Vous pouvez augmenter le nombre de pods dans votre déploiement en appliquant un nouveau fichier YAML.
Ce fichier YAML définit `replicas` à 4, ce qui spécifie que le déploiement devrait avoir quatre pods :
-{{< codenew file="application/deployment-scale.yaml" >}}
+{{% codenew file="application/deployment-scale.yaml" %}}
1. Appliquez le nouveau fichier YAML :
diff --git a/content/fr/docs/tutorials/hello-minikube.md b/content/fr/docs/tutorials/hello-minikube.md
index f097b375a4..2c1b562405 100644
--- a/content/fr/docs/tutorials/hello-minikube.md
+++ b/content/fr/docs/tutorials/hello-minikube.md
@@ -39,9 +39,9 @@ Vous pouvez également suivre ce tutoriel si vous avez installé [Minikube local
Ce tutoriel fournit une image de conteneur construite à partir des fichiers suivants :
-{{< codenew language="js" file="minikube/server.js" >}}
+{{% codenew language="js" file="minikube/server.js" %}}
-{{< codenew language="conf" file="minikube/Dockerfile" >}}
+{{% codenew language="conf" file="minikube/Dockerfile" %}}
Pour plus d'informations sur la commande `docker build`, lisez la documentation de [Docker](https://docs.docker.com/engine/reference/commandline/build/).
From b28d0d607c6a9d7b81cb49577126833fed0a43a2 Mon Sep 17 00:00:00 2001
From: Andrey Goran
Date: Tue, 25 Jul 2023 12:32:37 +0400
Subject: [PATCH 073/446] IT localization: replaced {{< codenew ... >}} with
{{% codenew ... %}} in all files
---
.../it/docs/concepts/cluster-administration/logging.md | 10 +++++-----
.../cluster-administration/manage-deployment.md | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/it/docs/concepts/cluster-administration/logging.md b/content/it/docs/concepts/cluster-administration/logging.md
index 931eb1c2cb..083cbf11dc 100644
--- a/content/it/docs/concepts/cluster-administration/logging.md
+++ b/content/it/docs/concepts/cluster-administration/logging.md
@@ -28,7 +28,7 @@ emette i dati sul flusso di output standard. Utilizza questa dimostrazione
una [specifica pod](/esempi/debug/counter-pod.yaml) con
un contenitore che scrive del testo sullo standard output una volta al secondo.
-{{< codenew file="debug/counter-pod.yaml" >}}
+{{% codenew file="debug/counter-pod.yaml" %}}
Per eseguire questo pod, utilizzare il seguente comando:
@@ -160,7 +160,7 @@ Considera il seguente esempio. Un pod esegue un singolo contenitore e il conteni
scrive su due file di registro diversi, utilizzando due formati diversi. Ecco un
file di configurazione per il pod:
-{{< codenew file="admin/logging/two-files-counter-pod.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod.yaml" %}}
Sarebbe un disastro avere voci di registro di diversi formati nello stesso registro
stream, anche se si è riusciti a reindirizzare entrambi i componenti al flusso `stdout` di
@@ -170,7 +170,7 @@ i registri al proprio flusso `stdout`.
Ecco un file di configurazione per un pod con due contenitori sidecar:
-{{< codenew file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" %}}
Ora quando si esegue questo pod, è possibile accedere separatamente a ciascun flusso di log
eseguendo i seguenti comandi:
@@ -229,7 +229,7 @@ che utilizza fluentd come agente di registrazione. Qui ci sono due file di confi
puoi usare per implementare questo approccio. Il primo file contiene
a [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) per configurare fluentd.
-{{< codenew file="admin/logging/fluentd-sidecar-config.yaml" >}}
+{{% codenew file="admin/logging/fluentd-sidecar-config.yaml" %}}
{{< note >}}
La configurazione di fluentd esula dallo scopo di questo articolo. Per
@@ -240,7 +240,7 @@ informazioni sulla configurazione di fluentd, vedere il
Il secondo file descrive un pod con un contenitore sidecar in esecuzione fluentd.
Il pod monta un volume dove fluentd può raccogliere i suoi dati di configurazione.
-{{< codenew file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" %}}
Dopo un po 'di tempo è possibile trovare i messaggi di registro nell'interfaccia Stackdriver.
diff --git a/content/it/docs/concepts/cluster-administration/manage-deployment.md b/content/it/docs/concepts/cluster-administration/manage-deployment.md
index f2e6dbb309..568fabf9f6 100644
--- a/content/it/docs/concepts/cluster-administration/manage-deployment.md
+++ b/content/it/docs/concepts/cluster-administration/manage-deployment.md
@@ -21,7 +21,7 @@ e [labels](/docs/concepts/overview/working-with-objects/labels/).
Molte applicazioni richiedono la creazione di più risorse, ad esempio una distribuzione e un servizio. La gestione di più risorse può essere semplificata raggruppandole nello stesso file (separate da `---` in YAML). Per esempio:
-{{< codenew file="application/nginx-app.yaml" >}}
+{{% codenew file="application/nginx-app.yaml" %}}
Multiple resources can be created the same way as a single resource:
From 9efc24421a149071b8c2b3224bc27bb6f32875bd Mon Sep 17 00:00:00 2001
From: Evan Lezar
Date: Tue, 25 Jul 2023 12:13:21 +0200
Subject: [PATCH 074/446] Update
content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
Co-authored-by: Mengjiao Liu <44460091+mengjiao-liu@users.noreply.github.com>
---
.../extend-kubernetes/compute-storage-net/device-plugins.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 f07ecc8fcb..bd046231f2 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
@@ -161,7 +161,7 @@ The general workflow of a device plugin includes the following steps:
The processing of the fully-qualified CDI device names by the Device Manager requires
the `DevicePluginCDIDevices` feature gate to be enabled. This was added as an alpha feature in
v1.28.
- {{< note >}}
+ {{< /note >}}
### Handling kubelet restarts
From 29b7887d38447bb83af8da708ad7b331c98c3284 Mon Sep 17 00:00:00 2001
From: Gunju Kim
Date: Tue, 25 Jul 2023 21:21:13 +0900
Subject: [PATCH 075/446] Mark ExpandedDNSConfig feature to stable
---
content/en/docs/concepts/services-networking/dns-pod-service.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/services-networking/dns-pod-service.md b/content/en/docs/concepts/services-networking/dns-pod-service.md
index 731e593628..a63ef77629 100644
--- a/content/en/docs/concepts/services-networking/dns-pod-service.md
+++ b/content/en/docs/concepts/services-networking/dns-pod-service.md
@@ -325,7 +325,7 @@ options ndots:5
## DNS search domain list limits
-{{< feature-state for_k8s_version="1.26" state="beta" >}}
+{{< feature-state for_k8s_version="1.28" state="stable" >}}
Kubernetes itself does not limit the DNS Config until the length of the search
domain list exceeds 32 or the total length of all search domains exceeds 2048.
From 508ce4282f2b86c78bf47f7f3404edbcfdf282f2 Mon Sep 17 00:00:00 2001
From: Humble Chirammal
Date: Tue, 25 Jul 2023 18:04:28 +0530
Subject: [PATCH 076/446] mention CephFS and RBD in-tree storage driver
deprecation.
Signed-off-by: Humble Chirammal
---
.../en/docs/concepts/storage/persistent-volumes.md | 14 ++++++++------
.../en/docs/concepts/storage/storage-classes.md | 5 +++++
content/en/docs/concepts/storage/volumes.md | 12 +++++++++++-
3 files changed, 24 insertions(+), 7 deletions(-)
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index dfa08602f8..770bc4d29a 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -375,7 +375,7 @@ the following types of volumes:
* {{< glossary_tooltip text="csi" term_id="csi" >}}
* flexVolume (deprecated)
* gcePersistentDisk
-* rbd
+* rbd ( **deprecated** in v1.28)
* portworxVolume
You can only expand a PVC if its storage class's `allowVolumeExpansion` field is set to true.
@@ -505,7 +505,6 @@ Kubernetes does not support shrinking a PVC to less than its current size.
PersistentVolume types are implemented as plugins. Kubernetes currently supports the following plugins:
-* [`cephfs`](/docs/concepts/storage/volumes/#cephfs) - CephFS volume
* [`csi`](/docs/concepts/storage/volumes/#csi) - Container Storage Interface (CSI)
* [`fc`](/docs/concepts/storage/volumes/#fc) - Fibre Channel (FC) storage
* [`hostPath`](/docs/concepts/storage/volumes/#hostpath) - HostPath volume
@@ -515,7 +514,6 @@ PersistentVolume types are implemented as plugins. Kubernetes currently supports
* [`local`](/docs/concepts/storage/volumes/#local) - local storage devices
mounted on nodes.
* [`nfs`](/docs/concepts/storage/volumes/#nfs) - Network File System (NFS) storage
-* [`rbd`](/docs/concepts/storage/volumes/#rbd) - Rados Block Device (RBD) volume
The following types of PersistentVolume are deprecated.
This means that support is still available but will be removed in a future Kubernetes release.
@@ -536,6 +534,10 @@ This means that support is still available but will be removed in a future Kuber
(**deprecated** in v1.25)
* [`vsphereVolume`](/docs/concepts/storage/volumes/#vspherevolume) - vSphere VMDK volume
(**deprecated** in v1.19)
+* [`cephfs`](/docs/concepts/storage/volumes/#cephfs) - CephFS volume
+ (**deprecated** in v1.28)
+* [`rbd`](/docs/concepts/storage/volumes/#rbd) - Rados Block Device (RBD) volume
+ (**deprecated** in v1.28)
Older versions of Kubernetes also supported the following in-tree PersistentVolume types:
@@ -726,12 +728,12 @@ The following volume types support mount options:
* `awsElasticBlockStore`
* `azureDisk`
* `azureFile`
-* `cephfs`
+* `cephfs` ( **deprecated** in v1.28)
* `cinder` (**deprecated** in v1.18)
* `gcePersistentDisk`
* `iscsi`
* `nfs`
-* `rbd`
+* `rbd` ( **deprecated** in v1.28)
* `vsphereVolume`
Mount options are not validated. If a mount option is invalid, the mount fails.
@@ -952,7 +954,7 @@ applicable:
* iSCSI
* Local volume
* OpenStack Cinder
-* RBD (Ceph Block Device)
+* RBD (Ceph Block Device) ( **deprecated** in v1.28)
* VsphereVolume
### PersistentVolume using a Raw Block Volume {#persistent-volume-using-a-raw-block-volume}
diff --git a/content/en/docs/concepts/storage/storage-classes.md b/content/en/docs/concepts/storage/storage-classes.md
index 70f37d2f66..200a88be19 100644
--- a/content/en/docs/concepts/storage/storage-classes.md
+++ b/content/en/docs/concepts/storage/storage-classes.md
@@ -471,6 +471,11 @@ There are few
which you try out for persistent volume management inside Kubernetes for vSphere.
### Ceph RBD
+{{< note >}}
+{{< feature-state state="deprecated" for_k8s_version="v1.28" >}}
+This internal provisioner of Ceph RBD is deprecated. Please use
+[CephFS RBD CSI driver](https://github.com/ceph/ceph-csi).
+{{< /note >}}
```yaml
apiVersion: storage.k8s.io/v1
diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index ba04f037a5..46167eb9f2 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -190,6 +190,11 @@ To disable the `azureFile` storage plugin from being loaded by the controller ma
and the kubelet, set the `InTreePluginAzureFileUnregister` flag to `true`.
### cephfs
+{{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
+
+{{< note >}}
+The Kubernetes project recommends to use [CephFS CSI](https://github.com/ceph/ceph-csi) out-of-tree driver instead.
+{{< /note >}}
A `cephfs` volume allows an existing CephFS volume to be
mounted into your Pod. Unlike `emptyDir`, which is erased when a pod is
@@ -865,6 +870,11 @@ A projected volume maps several existing volume sources into the same
directory. For more details, see [projected volumes](/docs/concepts/storage/projected-volumes/).
### rbd
+{{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
+
+{{< note >}}
+The Kubernetes project recommends to use [Ceph RBD CSI](https://github.com/ceph/ceph-csi) out-of-tree driver instead.
+{{< /note >}}
An `rbd` volume allows a
[Rados Block Device](https://docs.ceph.com/en/latest/rbd/) (RBD) volume to mount
@@ -943,7 +953,7 @@ For more details, see [Configuring Secrets](/docs/concepts/configuration/secret/
### vsphereVolume (deprecated) {#vspherevolume}
{{< note >}}
-We recommend to use vSphere CSI out-of-tree driver instead.
+The Kubernetes project recommends to use vSphere CSI out-of-tree driver instead.
{{< /note >}}
A `vsphereVolume` is used to mount a vSphere VMDK volume into your Pod. The contents
From 88b73643c48b30b14006fc53fa668003d4036243 Mon Sep 17 00:00:00 2001
From: shubham82
Date: Tue, 25 Jul 2023 18:40:57 +0530
Subject: [PATCH 077/446] Add the hyperlink to DeletionPolicy.
---
.../en/docs/concepts/storage/volume-snapshot-classes.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/en/docs/concepts/storage/volume-snapshot-classes.md b/content/en/docs/concepts/storage/volume-snapshot-classes.md
index 705d7bbaa6..41c7d8b56a 100644
--- a/content/en/docs/concepts/storage/volume-snapshot-classes.md
+++ b/content/en/docs/concepts/storage/volume-snapshot-classes.md
@@ -74,10 +74,10 @@ used for provisioning VolumeSnapshots. This field must be specified.
### DeletionPolicy
-Volume snapshot classes have a deletionPolicy. It enables you to configure what
-happens to a VolumeSnapshotContent when the VolumeSnapshot object it is bound to
-is to be deleted. The deletionPolicy of a volume snapshot class can either be
-`Retain` or `Delete`. This field must be specified.
+Volume snapshot classes have a [deletionPolicy](/docs/concepts/storage/volume-snapshots/ #delete).
+It enables you to configure what happens to a VolumeSnapshotContent when the VolumeSnapshot
+object it is bound to is to be deleted. The deletionPolicy of a volume snapshot class can
+either be `Retain` or `Delete`. This field must be specified.
If the deletionPolicy is `Delete`, then the underlying storage snapshot will be
deleted along with the VolumeSnapshotContent object. If the deletionPolicy is `Retain`,
From c02a114c341f7b45501264227736a5f8705a2534 Mon Sep 17 00:00:00 2001
From: Han Kang
Date: Thu, 20 Jul 2023 16:07:43 -0700
Subject: [PATCH 078/446] update documented metrics
---
.../docs/reference/instrumentation/metrics.md | 402 +++++++++++++-----
1 file changed, 295 insertions(+), 107 deletions(-)
diff --git a/content/en/docs/reference/instrumentation/metrics.md b/content/en/docs/reference/instrumentation/metrics.md
index 0cc90d8d78..4b5ae9fc9a 100644
--- a/content/en/docs/reference/instrumentation/metrics.md
+++ b/content/en/docs/reference/instrumentation/metrics.md
@@ -6,16 +6,16 @@ description: >-
Details of the metric data that Kubernetes components export.
---
-## Metrics (v1.27)
+## Metrics (v1.28)
-
-
+
+
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.
+Stable metrics observe strict API contracts and no labels can be added or removed from stable metrics during their lifetime.
@@ -225,8 +225,7 @@ Stable metrics observe strict API contracts and no labels can be added or remove
### 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.
-
+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.
@@ -242,12 +241,103 @@ Beta metrics observe a looser API contract than its stable counterparts. No labe
+
apiserver_flowcontrol_current_executing_requests
+
BETA
+
Gauge
+
Number of requests in initial (for a WATCH) or any (for a non-WATCH) execution stage in the API Priority and Fairness subsystem
+
flow_schema
priority_level
+
+
+
apiserver_flowcontrol_current_executing_seats
+
BETA
+
Gauge
+
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
+
flow_schema
priority_level
+
+
+
apiserver_flowcontrol_current_inqueue_requests
+
BETA
+
Gauge
+
Number of requests currently pending in queues of the API Priority and Fairness subsystem
+
flow_schema
priority_level
+
+
+
apiserver_flowcontrol_dispatched_requests_total
+
BETA
+
Counter
+
Number of requests executed by API Priority and Fairness subsystem
+
flow_schema
priority_level
+
+
+
apiserver_flowcontrol_nominal_limit_seats
+
BETA
+
Gauge
+
Nominal number of execution seats configured for each priority level
+
priority_level
+
+
+
apiserver_flowcontrol_rejected_requests_total
+
BETA
+
Counter
+
Number of requests rejected by API Priority and Fairness subsystem
Length of time a request spent waiting in its queue
+
execute
flow_schema
priority_level
+
+
+
disabled_metrics_total
+
BETA
+
Counter
+
The count of disabled metrics.
+
+
+
+
hidden_metrics_total
+
BETA
+
Counter
+
The count of hidden metrics.
+
+
+
+
kubernetes_feature_enabled
+
BETA
+
Gauge
+
This metric records the data about the stage and enablement of a k8s feature.
+
name
stage
+
+
+
kubernetes_healthcheck
+
BETA
+
Gauge
+
This metric records the result of a single healthcheck.
+
name
type
+
+
+
kubernetes_healthchecks_total
+
BETA
+
Counter
+
This metric records the results of all healthcheck.
+
name
status
type
+
+
+
registered_metrics_total
+
BETA
+
Counter
+
The count of registered metrics broken by stability level and deprecation version.
+
deprecated_version
stability_level
+
+
### 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.
+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.
@@ -312,11 +402,25 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
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).
-
name
type
+
Admission match condition evaluation errors count, identified by name of resource containing the match condition and broken out for each kind containing matchConditions (webhook or policy), operation and admission type (validate or admit).
Admission match condition evaluation time in seconds, identified by name and broken out for each kind containing matchConditions (webhook or policy), operation and type (validate or admit).
Admission match condition evaluation exclusions count, identified by name of resource containing the match condition and broken out for each kind containing matchConditions (webhook or policy), operation and admission type (validate or admit).
@@ -683,27 +794,20 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
phase
request_kind
-
apiserver_flowcontrol_rejected_requests_total
-
ALPHA
-
Counter
-
Number of requests rejected by API Priority and Fairness subsystem
-
flow_schema
priority_level
reason
-
-
apiserver_flowcontrol_request_concurrency_in_use
ALPHA
Gauge
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
flow_schema
priority_level
-
+
1.31.0
apiserver_flowcontrol_request_concurrency_limit
ALPHA
Gauge
-
Shared concurrency limit in the API Priority and Fairness subsystem
+
Nominal number of execution seats configured for each priority level
Length of time a request spent waiting in its queue
-
execute
flow_schema
priority_level
-
-
apiserver_flowcontrol_seat_fair_frac
ALPHA
Gauge
@@ -844,6 +941,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
code_path
+
apiserver_rerouted_request_total
+
ALPHA
+
Counter
+
Total number of requests that were proxied to a peer kube apiserver because the local apiserver was not capable of serving it
+
code
+
+
apiserver_selfrequest_total
ALPHA
Counter
@@ -871,7 +975,7 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
Total size of the storage database file physically allocated in bytes.
endpoint
-
+
1.28.0
apiserver_storage_decode_errors_total
ALPHA
Counter
@@ -921,6 +1025,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
resource
+
apiserver_storage_size_bytes
+
ALPHA
+
Custom
+
Size of the storage database file physically allocated in bytes.
+
cluster
+
+
apiserver_storage_transformation_duration_seconds
ALPHA
Histogram
@@ -931,7 +1042,7 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
apiserver_storage_transformation_operations_total
ALPHA
Counter
-
Total number of transformations.
+
Total number of transformations. Successful transformation will have a status 'OK' and a varied status string when the transformation fails. This status and transformation_type fields may be used for alerting on encryption/decryption failure using transformation_type from_storage for decryption and to_storage for encryption
status
transformation_type
transformer_prefix
@@ -1019,11 +1130,11 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
Cumulative number of errors when starting hostprocess containers. This metric will only be collected on Windows and requires WindowsHostProcessContainers feature gate to be enabled.
+
Cumulative number of errors when starting hostprocess containers. This metric will only be collected on Windows.
code
container_type
kubelet_started_host_process_containers_total
ALPHA
Counter
-
Cumulative number of hostprocess containers started. This metric will only be collected on Windows and requires WindowsHostProcessContainers feature gate to be enabled.
+
Cumulative number of hostprocess containers started. This metric will only be collected on Windows.
container_type
@@ -2083,6 +2215,34 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
+
kubeproxy_proxy_healthz_total
+
ALPHA
+
Counter
+
Cumulative proxy healthz HTTP status
+
code
+
+
+
kubeproxy_proxy_livez_total
+
ALPHA
+
Counter
+
Cumulative proxy livez HTTP status
+
code
+
+
+
kubeproxy_sync_full_proxy_rules_duration_seconds
+
ALPHA
+
Histogram
+
SyncProxyRules latency in seconds for full resyncs
Number of seconds after node creation when NodeController removed the cloud-provider taint of a single node.
+
+
+
+
node_controller_initial_node_sync_delay_seconds
+
ALPHA
+
Histogram
+
Number of seconds after node creation when NodeController finished the initial synchronization of a single node.
+
+
+
node_cpu_usage_seconds_total
ALPHA
Custom
@@ -2321,6 +2481,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
+
node_swap_usage_bytes
+
ALPHA
+
Custom
+
Current swap usage of the node in bytes. Reported only on non-windows systems
+
+
+
number_of_l4_ilbs
ALPHA
Gauge
@@ -2346,14 +2513,14 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
ALPHA
Counter
Number of errors encountered when forcefully deleting the pods since the Pod GC Controller started.
-
+
namespace
reason
pod_gc_collector_force_delete_pods_total
ALPHA
Counter
Number of pods that are being forcefully deleted since the Pod GC Controller started.
-
+
namespace
reason
pod_memory_working_set_bytes
@@ -2384,6 +2551,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
request_operation
resource
subresource
+
pod_swap_usage_bytes
+
ALPHA
+
Custom
+
Current amount of the pod swap usage in bytes. Reported only on non-windows systems
+
pod
namespace
+
+
prober_probe_duration_seconds
ALPHA
Histogram
@@ -2468,6 +2642,13 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
+
rest_client_dns_resolution_duration_seconds
+
ALPHA
+
Histogram
+
DNS resolver latency in seconds. Broken down by host.
+
host
+
+
rest_client_exec_plugin_call_total
ALPHA
Counter
@@ -2531,6 +2712,20 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
host
verb
+
rest_client_transport_cache_entries
+
ALPHA
+
Gauge
+
Number of transport entries in the internal cache.
+
+
+
+
rest_client_transport_create_calls_total
+
ALPHA
+
Counter
+
Number of calls to get a new transport, partitioned by the result of the operation hit: obtained from the cache, miss: created and added to the cache, uncacheable: created and not cached
+
result
+
+
retroactive_storageclass_errors_total
ALPHA
Counter
@@ -2601,13 +2796,6 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
type
-
scheduler_scheduler_goroutines
-
ALPHA
-
Gauge
-
Number of running goroutines split by the work they do such as binding. This metric is replaced by the \"goroutines\" metric.
-
work
-
-
1.26.0
scheduler_scheduling_algorithm_duration_seconds
ALPHA
Histogram
From 6c234b0516b0ee0be66656eeeba68faa03ca596b Mon Sep 17 00:00:00 2001
From: Jordan Liggitt
Date: Tue, 25 Jul 2023 13:07:02 -0400
Subject: [PATCH 079/446] Update skew policy for n-3 nodes for 1.28/1.25+
---
content/en/releases/version-skew-policy.md | 24 ++++++++++++----------
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/content/en/releases/version-skew-policy.md b/content/en/releases/version-skew-policy.md
index ca065ee987..7a9f1c753a 100644
--- a/content/en/releases/version-skew-policy.md
+++ b/content/en/releases/version-skew-policy.md
@@ -45,12 +45,13 @@ Example:
### kubelet
-`kubelet` must not be newer than `kube-apiserver`, and may be up to two minor versions older.
+* `kubelet` must not be newer than `kube-apiserver`.
+* `kubelet` may be up to three minor versions older than `kube-apiserver` (`kubelet` < 1.25 may only be up to two minor versions older than `kube-apiserver`).
Example:
* `kube-apiserver` is at **{{< skew currentVersion >}}**
-* `kubelet` is supported at **{{< skew currentVersion >}}**, **{{< skew currentVersionAddMinor -1 >}}**, and **{{< skew currentVersionAddMinor -2 >}}**
+* `kubelet` is supported at **{{< skew currentVersion >}}**, **{{< skew currentVersionAddMinor -1 >}}**, **{{< skew currentVersionAddMinor -2 >}}**, and **{{< skew currentVersionAddMinor -3 >}}**
{{< note >}}
If version skew exists between `kube-apiserver` instances in an HA cluster, this narrows the allowed `kubelet` versions.
@@ -59,17 +60,18 @@ If version skew exists between `kube-apiserver` instances in an HA cluster, this
Example:
* `kube-apiserver` instances are at **{{< skew currentVersion >}}** and **{{< skew currentVersionAddMinor -1 >}}**
-* `kubelet` is supported at **{{< skew currentVersionAddMinor -1 >}}**, and **{{< skew currentVersionAddMinor -2 >}}** (**{{< skew currentVersion >}}** is not supported because that would be newer than the `kube-apiserver` instance at version **{{< skew currentVersionAddMinor -1 >}}**)
+* `kubelet` is supported at **{{< skew currentVersionAddMinor -1 >}}**, **{{< skew currentVersionAddMinor -2 >}}**, and **{{< skew currentVersionAddMinor -3 >}}** (**{{< skew currentVersion >}}** is not supported because that would be newer than the `kube-apiserver` instance at version **{{< skew currentVersionAddMinor -1 >}}**)
### kube-proxy
-`kube-proxy` must not be newer than `kube-apiserver`, and may be up to two minor versions older.
-`kube-proxy` may be up to two minor versions older or newer than the `kubelet` instance it runs alongside.
+* `kube-proxy` must not be newer than `kube-apiserver`.
+* `kube-proxy` may be up to three minor versions older than `kube-apiserver` (`kube-proxy` < 1.25 may only be up to two minor versions older than `kube-apiserver`).
+* `kube-proxy` may be up to three minor versions older or newer than the `kubelet` instance it runs alongside (`kube-proxy` < 1.25 may only be up to two minor versions older or newer than the `kubelet` instance it runs alongside).
Example:
* `kube-apiserver` is at **{{< skew currentVersion >}}**
-* `kube-proxy` is supported at **{{< skew currentVersion >}}**, **{{< skew currentVersionAddMinor -1 >}}**, and **{{< skew currentVersionAddMinor -2 >}}**
+* `kube-proxy` is supported at **{{< skew currentVersion >}}**, **{{< skew currentVersionAddMinor -1 >}}**, **{{< skew currentVersionAddMinor -2 >}}**, and **{{< skew currentVersionAddMinor -3 >}}**
{{< note >}}
If version skew exists between `kube-apiserver` instances in an HA cluster, this narrows the allowed `kube-proxy` versions.
@@ -78,7 +80,7 @@ If version skew exists between `kube-apiserver` instances in an HA cluster, this
Example:
* `kube-apiserver` instances are at **{{< skew currentVersion >}}** and **{{< skew currentVersionAddMinor -1 >}}**
-* `kube-proxy` is supported at **{{< skew currentVersionAddMinor -1 >}}**, and **{{< skew currentVersionAddMinor -2 >}}** (**{{< skew currentVersion >}}** is not supported because that would be newer than the `kube-apiserver` instance at version **{{< skew currentVersionAddMinor -1 >}}**)
+* `kube-proxy` is supported at **{{< skew currentVersionAddMinor -1 >}}**, **{{< skew currentVersionAddMinor -2 >}}**, and **{{< skew currentVersionAddMinor -3 >}}** (**{{< skew currentVersion >}}** is not supported because that would be newer than the `kube-apiserver` instance at version **{{< skew currentVersionAddMinor -1 >}}**)
### kube-controller-manager, kube-scheduler, and cloud-controller-manager
@@ -173,7 +175,7 @@ Pre-requisites:
* The `kube-apiserver` instances the `kubelet` communicates with are at **{{< skew currentVersion >}}**
-Optionally upgrade `kubelet` instances to **{{< skew currentVersion >}}** (or they can be left at **{{< skew currentVersionAddMinor -1 >}}** or **{{< skew currentVersionAddMinor -2 >}}**)
+Optionally upgrade `kubelet` instances to **{{< skew currentVersion >}}** (or they can be left at **{{< skew currentVersionAddMinor -1 >}}**, **{{< skew currentVersionAddMinor -2 >}}**, or **{{< skew currentVersionAddMinor -3 >}}**)
{{< note >}}
Before performing a minor version `kubelet` upgrade, [drain](/docs/tasks/administer-cluster/safely-drain-node/) pods from that node.
@@ -181,7 +183,7 @@ In-place minor version `kubelet` upgrades are not supported.
{{ note >}}
{{< warning >}}
-Running a cluster with `kubelet` instances that are persistently two minor versions behind `kube-apiserver` means they must be upgraded before the control plane can be upgraded.
+Running a cluster with `kubelet` instances that are persistently three minor versions behind `kube-apiserver` means they must be upgraded before the control plane can be upgraded.
{{ warning >}}
### kube-proxy
@@ -190,8 +192,8 @@ Pre-requisites:
* The `kube-apiserver` instances `kube-proxy` communicates with are at **{{< skew currentVersion >}}**
-Optionally upgrade `kube-proxy` instances to **{{< skew currentVersion >}}** (or they can be left at **{{< skew currentVersionAddMinor -1 >}}** or **{{< skew currentVersionAddMinor -2 >}}**)
+Optionally upgrade `kube-proxy` instances to **{{< skew currentVersion >}}** (or they can be left at **{{< skew currentVersionAddMinor -1 >}}**, **{{< skew currentVersionAddMinor -2 >}}**, or **{{< skew currentVersionAddMinor -3 >}}**)
{{< warning >}}
-Running a cluster with `kube-proxy` instances that are persistently two minor versions behind `kube-apiserver` means they must be upgraded before the control plane can be upgraded.
+Running a cluster with `kube-proxy` instances that are persistently three minor versions behind `kube-apiserver` means they must be upgraded before the control plane can be upgraded.
{{ warning >}}
From 9bac8cfc1a9b8730bc37f1d8705b94301e101b1c Mon Sep 17 00:00:00 2001
From: Amine
Date: Tue, 25 Jul 2023 19:54:51 +0100
Subject: [PATCH 080/446] Add note on max number of match condition elements a
user can define per webhook
---
.../access-authn-authz/extensible-admission-controllers.md | 4 ++++
1 file changed, 4 insertions(+)
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 b909bb131f..73b29690f4 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
@@ -738,6 +738,10 @@ Here is an example illustrating a few different uses for match conditions:
{{< codenew file="access/validating-webhook-configuration-match-conditions.yaml" >}}
+{{< note >}}
+You can define up to 64 elements in the `matchConditions`` field per webhook.
+{{< /note >}}
+
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
From 058033eaa38dbc3c8731913b60198074966da430 Mon Sep 17 00:00:00 2001
From: shubham82
Date: Wed, 26 Jul 2023 11:56:04 +0530
Subject: [PATCH 081/446] Correct the hyperlink
---
content/en/docs/concepts/storage/volume-snapshot-classes.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/storage/volume-snapshot-classes.md b/content/en/docs/concepts/storage/volume-snapshot-classes.md
index 41c7d8b56a..48d48b81f4 100644
--- a/content/en/docs/concepts/storage/volume-snapshot-classes.md
+++ b/content/en/docs/concepts/storage/volume-snapshot-classes.md
@@ -74,7 +74,7 @@ used for provisioning VolumeSnapshots. This field must be specified.
### DeletionPolicy
-Volume snapshot classes have a [deletionPolicy](/docs/concepts/storage/volume-snapshots/ #delete).
+Volume snapshot classes have a [deletionPolicy](/docs/concepts/storage/volume-snapshots/#delete).
It enables you to configure what happens to a VolumeSnapshotContent when the VolumeSnapshot
object it is bound to is to be deleted. The deletionPolicy of a volume snapshot class can
either be `Retain` or `Delete`. This field must be specified.
From 0d2962b0f80ab626209788d1c00cfabc91c09dae Mon Sep 17 00:00:00 2001
From: Markus Lehtonen
Date: Wed, 26 Jul 2023 11:18:14 +0300
Subject: [PATCH 082/446] docs: change wording of k8s versioning on
KubeletCgroupDriverFromCRI
---
.../docs/setup/production-environment/container-runtimes.md | 6 +++---
.../administer-cluster/kubeadm/configure-cgroup-driver.md | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/en/docs/setup/production-environment/container-runtimes.md b/content/en/docs/setup/production-environment/container-runtimes.md
index ce49a7347d..36bf4ef299 100644
--- a/content/en/docs/setup/production-environment/container-runtimes.md
+++ b/content/en/docs/setup/production-environment/container-runtimes.md
@@ -157,7 +157,7 @@ Starting with v1.22 and later, when creating a cluster with kubeadm, if the user
the `cgroupDriver` field under `KubeletConfiguration`, kubeadm defaults it to `systemd`.
{{< /note >}}
-For Kubernetes v1.28 and later, with the `KubeletCgroupDriverFromCRI`
+In Kubernetes {{< skew currentVersion >}}, with the `KubeletCgroupDriverFromCRI`
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
enabled and a container runtime that supports the `RuntimeConfig` CRI RPC,
the kubelet automatically detects the appropriate cgroup driver from the runtime,
@@ -257,7 +257,7 @@ sudo systemctl restart containerd
When using kubeadm, manually configure the
[cgroup driver for kubelet](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/#configuring-the-kubelet-cgroup-driver).
-Starting with v1.28 and later, you can enable automatic detection of the
+In Kubernetes {{< skew currentVersion >}}, you can enable automatic detection of the
cgroup driver as an alpha feature. See [systemd cgroup driver](#systemd-cgroup-driver)
for more details.
@@ -302,7 +302,7 @@ You should also note the changed `conmon_cgroup`, which has to be set to the val
cgroup driver configuration of the kubelet (usually done via kubeadm) and CRI-O
in sync.
-Starting with v1.28 and later, you can enable automatic detection of the
+In Kubernetes {{< skew currentVersion >}}, you can enable automatic detection of the
cgroup driver as an alpha feature. See [systemd cgroup driver](#systemd-cgroup-driver)
for more details.
diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
index e3133054f5..afaa370011 100644
--- a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
+++ b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
@@ -37,7 +37,7 @@ driver of the kubelet.
In v1.22 and later, if the user does not set the `cgroupDriver` field under `KubeletConfiguration`,
kubeadm defaults it to `systemd`.
-Starting with v1.28 and later, you can enable automatic detection of the
+In Kubernetes {{< skew currentVersion >}}, you can enable automatic detection of the
cgroup driver as an alpha feature.
See [systemd cgroup driver](/docs/setup/production-environment/container-runtimes/#systemd-cgroup-driver)
for more details.
From 551bb8ea68e965351284562364b7358a8c7479ea Mon Sep 17 00:00:00 2001
From: Richa Banker
Date: Mon, 24 Jul 2023 16:53:17 -0700
Subject: [PATCH 083/446] Add an entry in glossary for UVIP
---
.../reference/glossary/mixed-version-proxy.md | 21 +++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/en/docs/reference/glossary/mixed-version-proxy.md
diff --git a/content/en/docs/reference/glossary/mixed-version-proxy.md b/content/en/docs/reference/glossary/mixed-version-proxy.md
new file mode 100644
index 0000000000..33926e3f6e
--- /dev/null
+++ b/content/en/docs/reference/glossary/mixed-version-proxy.md
@@ -0,0 +1,21 @@
+---
+title: Mixed Version Proxy (MVP)
+id: mvp
+date: 2023-07-24
+full_link: /docs/concepts/architecture/mixed-version-proxy#Enabling-the-Mixed-Version-Proxy
+short_description: >
+ Feature that lets a kube-apiserver proxy a resource request to a different peer API server.
+aka: ["MVP"]
+tags:
+- architecture
+---
+Feature to let a kube-apiserver proxy a resource request to a different peer API server.
+
+
+
+When a cluster has multiple API servers running different versions of Kubernetes, this
+feature enables resource requests to be served by the correct API server.
+
+MVP is disabled by default and can be activated by enabling
+the feature gate named `UnknownVersionInteroperabilityProxy` when
+{{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}} is started.
From f1fe316eec07edb08b9e2cf7d9b6c9a0ec11d473 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Fri, 23 Jun 2023 09:56:44 -0400
Subject: [PATCH 084/446] add a section on podrecreationpolicy for jobs
---
.../concepts/workloads/controllers/job.md | 50 +++++++++++++++++++
1 file changed, 50 insertions(+)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index be6a66c9db..fd6572ba75 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -457,6 +457,12 @@ Since Kubernetes 1.27, Kubelet transitions deleted pods to a terminal phase
ensures that deleted pods have their finalizers removed by the Job controller.
{{< /note >}}
+{{< note >}}
+Since Kubernetes v1.28, when pod failure policy is used, the Job controller recreates
+terminating pods only once they reach the terminal `Failed` phase. This behavior is analogous
+to when using `podRecreationPolicy: Failed`, see [pod replacement policy](#pod-replacement-policy) for more details.
+{{< /note >}}
+
## Job termination and cleanup
When a Job completes, no more Pods are created, but the Pods are [usually](#pod-backoff-failure-policy) not deleted either.
@@ -867,6 +873,50 @@ 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.
+### Pod Replacement Policy
+
+{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
+
+{{< note >}}
+You can only enable `PodReplacementPolicy` for Jobs if you set `JobPodReplacementPolicy`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to true.
+{{< /note >}}
+
+By default, the Job controller recreates pods as soon they are either failed or terminating (have a deletion timestamp).
+This means that, at a given time, the number of running Pods for the Jobs can be greater than `parallelism` or, if using Indexed Jobs, more than one running Pod per index, if some of the Pods are terminating.
+
+You may choose to create replacement pods only when the terminating pod is fully terminal (has `status.phase: Failed`). To do this, set the `.spec.podReplacementPolicy: Failed`.
+This will only recreate pods once they are terminated.
+Default behavior will be to recreate upon deletion (`DeletionTimestamp != nil`).
+
+```yaml
+kind: Job
+metadata:
+ name: new
+ ...
+spec:
+ podReplacementPolicy: Failed
+ ...
+```
+
+You can inspect a new field in the JobStatus called `terminating`.
+This will report the number pods that are currently terminating and is easily viewable in the status.
+
+```shell
+kubectl get jobs/myjob -o yaml
+```
+
+```yaml
+apiVersion: batch/v1
+kind: Job
+# .metadata and .spec omitted
+status:
+ terminating: 1 # if pod is terminating
+```
+
+When [PodFailurePolicy](#pod-failure-policy) is enabled, a Job will have a default (and only this value is allowed) value of `Failed`.
+If `JobPodReplacementPolicy` is disabled and `podFailurePolicy` is enabled, a Job will wait for terminating pods to be fully terminated before marking the pod as failed.
+In this case, you will not be able to inspect the `terminating` field.
+
## Alternatives
### Bare Pods
From f09e80a4f97016b22b01a379c3894123ee408c3e Mon Sep 17 00:00:00 2001
From: Shannon Kularathna
Date: Fri, 7 Jul 2023 19:32:14 +0000
Subject: [PATCH 085/446] Move use cases higher on the page
---
.../en/docs/concepts/configuration/secret.md | 1261 +++++++++--------
1 file changed, 631 insertions(+), 630 deletions(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index cf76ed3f3f..b24c02ac79 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -67,636 +67,6 @@ The Kubernetes control plane also uses Secrets; for example,
[bootstrap token Secrets](#bootstrap-token-secrets) are a mechanism to
help automate node registration.
-### Alternatives to Secrets
-
-Rather than using a Secret to protect confidential data, you can pick from alternatives.
-
-Here are some of your options:
-
-- If your cloud-native component needs to authenticate to another application that you
- know is running within the same Kubernetes cluster, you can use a
- [ServiceAccount](/docs/reference/access-authn-authz/authentication/#service-account-tokens)
- and its tokens to identify your client.
-- There are third-party tools that you can run, either within or outside your cluster,
- that provide secrets management. For example, a service that Pods access over HTTPS,
- that reveals a secret if the client correctly authenticates (for example, with a ServiceAccount
- token).
-- For authentication, you can implement a custom signer for X.509 certificates, and use
- [CertificateSigningRequests](/docs/reference/access-authn-authz/certificate-signing-requests/)
- to let that custom signer issue certificates to Pods that need them.
-- You can use a [device plugin](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
- to expose node-local encryption hardware to a specific Pod. For example, you can schedule
- trusted Pods onto nodes that provide a Trusted Platform Module, configured out-of-band.
-
-You can also combine two or more of those options, including the option to use Secret objects themselves.
-
-For example: implement (or deploy) an {{< glossary_tooltip text="operator" term_id="operator-pattern" >}}
-that fetches short-lived session tokens from an external service, and then creates Secrets based
-on those short-lived session tokens. Pods running in your cluster can make use of the session tokens,
-and operator ensures they are valid. This separation means that you can run Pods that are unaware of
-the exact mechanisms for issuing and refreshing those session tokens.
-
-## Types of Secret {#secret-types}
-
-When creating a Secret, you can specify its type using the `type` field of
-the [Secret](/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1/)
-resource, or certain equivalent `kubectl` command line flags (if available).
-The Secret type is used to facilitate programmatic handling of the Secret data.
-
-Kubernetes provides several built-in types for some common usage scenarios.
-These types vary in terms of the validations performed and the constraints
-Kubernetes imposes on them.
-
-| Built-in Type | Usage |
-| ------------------------------------- | --------------------------------------- |
-| `Opaque` | arbitrary user-defined data |
-| `kubernetes.io/service-account-token` | ServiceAccount token |
-| `kubernetes.io/dockercfg` | serialized `~/.dockercfg` file |
-| `kubernetes.io/dockerconfigjson` | serialized `~/.docker/config.json` file |
-| `kubernetes.io/basic-auth` | credentials for basic authentication |
-| `kubernetes.io/ssh-auth` | credentials for SSH authentication |
-| `kubernetes.io/tls` | data for a TLS client or server |
-| `bootstrap.kubernetes.io/token` | bootstrap token data |
-
-You can define and use your own Secret type by assigning a non-empty string as the
-`type` value for a Secret object (an empty string is treated as an `Opaque` type).
-
-Kubernetes doesn't impose any constraints on the type name. However, if you
-are using one of the built-in types, you must meet all the requirements defined
-for that type.
-
-If you are defining a type of secret that's for public use, follow the convention
-and structure the secret type to have your domain name before the name, separated
-by a `/`. For example: `cloud-hosting.example.net/cloud-api-credentials`.
-
-### Opaque secrets
-
-`Opaque` is the default Secret type if omitted from a Secret configuration file.
-When you create a Secret using `kubectl`, you will use the `generic`
-subcommand to indicate an `Opaque` Secret type. For example, the following
-command creates an empty Secret of type `Opaque`.
-
-```shell
-kubectl create secret generic empty-secret
-kubectl get secret empty-secret
-```
-
-The output looks like:
-
-```
-NAME TYPE DATA AGE
-empty-secret Opaque 0 2m6s
-```
-
-The `DATA` column shows the number of data items stored in the Secret.
-In this case, `0` means you have created an empty Secret.
-
-### Service account token Secrets
-
-A `kubernetes.io/service-account-token` type of Secret is used to store a
-token credential that identifies a
-{{< glossary_tooltip text="service account" term_id="service-account" >}}.
-
-{{< note >}}
-Versions of Kubernetes before v1.22 automatically created credentials for
-accessing the Kubernetes API. This older mechanism was based on creating token
-Secrets that could then be mounted into running Pods.
-In more recent versions, including Kubernetes v{{< skew currentVersion >}}, API
-credentials are obtained directly by using the
-[TokenRequest](/docs/reference/kubernetes-api/authentication-resources/token-request-v1/)
-API, and are mounted into Pods using a
-[projected volume](/docs/reference/access-authn-authz/service-accounts-admin/#bound-service-account-token-volume).
-The tokens obtained using this method have bounded lifetimes, and are
-automatically invalidated when the Pod they are mounted into is deleted.
-
-You can still
-[manually create](/docs/tasks/configure-pod-container/configure-service-account/#manually-create-a-service-account-api-token)
-a service account token Secret; for example, if you need a token that never
-expires. However, using the
-[TokenRequest](/docs/reference/kubernetes-api/authentication-resources/token-request-v1/)
-subresource to obtain a token to access the API is recommended instead.
-You can use the
-[`kubectl create token`](/docs/reference/generated/kubectl/kubectl-commands#-em-token-em-)
-command to obtain a token from the `TokenRequest` API.
-{{< /note >}}
-
-You should only create a service account token Secret object
-if you can't use the `TokenRequest` API to obtain a token,
-and the security exposure of persisting a non-expiring token credential
-in a readable API object is acceptable to you.
-
-When using this Secret type, you need to ensure that the
-`kubernetes.io/service-account.name` annotation is set to an existing
-service account name. If you are creating both the ServiceAccount and
-the Secret objects, you should create the ServiceAccount object first.
-
-After the Secret is created, a Kubernetes {{< glossary_tooltip text="controller" term_id="controller" >}}
-fills in some other fields such as the `kubernetes.io/service-account.uid` annotation, and the
-`token` key in the `data` field, which is populated with an authentication token.
-
-The following example configuration declares a service account token Secret:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
- name: secret-sa-sample
- annotations:
- kubernetes.io/service-account.name: "sa-name"
-type: kubernetes.io/service-account-token
-data:
- # You can include additional key value pairs as you do with Opaque Secrets
- extra: YmFyCg==
-```
-
-After creating the Secret, wait for Kubernetes to populate the `token` key in the `data` field.
-
-See the [ServiceAccount](/docs/tasks/configure-pod-container/configure-service-account/)
-documentation for more information on how service accounts work.
-You can also check the `automountServiceAccountToken` field and the
-`serviceAccountName` field of the
-[`Pod`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
-for information on referencing service account credentials from within Pods.
-
-### Docker config Secrets
-
-You can use one of the following `type` values to create a Secret to
-store the credentials for accessing a container image registry:
-
-- `kubernetes.io/dockercfg`
-- `kubernetes.io/dockerconfigjson`
-
-The `kubernetes.io/dockercfg` type is reserved to store a serialized
-`~/.dockercfg` which is the legacy format for configuring Docker command line.
-When using this Secret type, you have to ensure the Secret `data` field
-contains a `.dockercfg` key whose value is content of a `~/.dockercfg` file
-encoded in the base64 format.
-
-The `kubernetes.io/dockerconfigjson` type is designed for storing a serialized
-JSON that follows the same format rules as the `~/.docker/config.json` file
-which is a new format for `~/.dockercfg`.
-When using this Secret type, the `data` field of the Secret object must
-contain a `.dockerconfigjson` key, in which the content for the
-`~/.docker/config.json` file is provided as a base64 encoded string.
-
-Below is an example for a `kubernetes.io/dockercfg` type of Secret:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
- name: secret-dockercfg
-type: kubernetes.io/dockercfg
-data:
- .dockercfg: |
- ""
-```
-
-{{< note >}}
-If you do not want to perform the base64 encoding, you can choose to use the
-`stringData` field instead.
-{{< /note >}}
-
-When you create these types of Secrets using a manifest, the API
-server checks whether the expected key exists in the `data` field, and
-it verifies if the value provided can be parsed as a valid JSON. The API
-server doesn't validate if the JSON actually is a Docker config file.
-
-When you do not have a Docker config file, or you want to use `kubectl`
-to create a Secret for accessing a container registry, you can do:
-
-```shell
-kubectl create secret docker-registry secret-tiger-docker \
- --docker-email=tiger@acme.example \
- --docker-username=tiger \
- --docker-password=pass1234 \
- --docker-server=my-registry.example:5000
-```
-
-That command creates a Secret of type `kubernetes.io/dockerconfigjson`.
-If you dump the `.data.dockerconfigjson` field from that new Secret and then
-decode it from base64:
-
-```shell
-kubectl get secret secret-tiger-docker -o jsonpath='{.data.*}' | base64 -d
-```
-
-then the output is equivalent to this JSON document (which is also a valid
-Docker configuration file):
-
-```json
-{
- "auths": {
- "my-registry.example:5000": {
- "username": "tiger",
- "password": "pass1234",
- "email": "tiger@acme.example",
- "auth": "dGlnZXI6cGFzczEyMzQ="
- }
- }
-}
-```
-
-{{< note >}}
-The `auth` value there is base64 encoded; it is obscured but not secret.
-Anyone who can read that Secret can learn the registry access bearer token.
-{{< /note >}}
-
-### Basic authentication Secret
-
-The `kubernetes.io/basic-auth` type is provided for storing credentials needed
-for basic authentication. When using this Secret type, the `data` field of the
-Secret must contain one of the following two keys:
-
-- `username`: the user name for authentication
-- `password`: the password or token for authentication
-
-Both values for the above two keys are base64 encoded strings. You can, of
-course, provide the clear text content using the `stringData` for Secret
-creation.
-
-The following manifest is an example of a basic authentication Secret:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
- name: secret-basic-auth
-type: kubernetes.io/basic-auth
-stringData:
- username: admin # required field for kubernetes.io/basic-auth
- password: t0p-Secret # required field for kubernetes.io/basic-auth
-```
-
-The basic authentication Secret type is provided only for convenience.
-You can create an `Opaque` type for credentials used for basic authentication.
-However, using the defined and public Secret type (`kubernetes.io/basic-auth`) helps other
-people to understand the purpose of your Secret, and sets a convention for what key names
-to expect.
-The Kubernetes API verifies that the required keys are set for a Secret of this type.
-
-### SSH authentication secrets
-
-The builtin type `kubernetes.io/ssh-auth` is provided for storing data used in
-SSH authentication. When using this Secret type, you will have to specify a
-`ssh-privatekey` key-value pair in the `data` (or `stringData`) field
-as the SSH credential to use.
-
-The following manifest is an example of a Secret used for SSH public/private
-key authentication:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
- name: secret-ssh-auth
-type: kubernetes.io/ssh-auth
-data:
- # the data is abbreviated in this example
- ssh-privatekey: |
- MIIEpQIBAAKCAQEAulqb/Y ...
-```
-
-The SSH authentication Secret type is provided only for user's convenience.
-You could instead create an `Opaque` type Secret for credentials used for SSH authentication.
-However, using the defined and public Secret type (`kubernetes.io/ssh-auth`) helps other
-people to understand the purpose of your Secret, and sets a convention for what key names
-to expect.
-and the API server does verify if the required keys are provided in a Secret configuration.
-
-{{< caution >}}
-SSH private keys do not establish trusted communication between an SSH client and
-host server on their own. A secondary means of establishing trust is needed to
-mitigate "man in the middle" attacks, such as a `known_hosts` file added to a ConfigMap.
-{{< /caution >}}
-
-### TLS secrets
-
-Kubernetes provides a builtin Secret type `kubernetes.io/tls` for storing
-a certificate and its associated key that are typically used for TLS.
-
-One common use for TLS secrets is to configure encryption in transit for
-an [Ingress](/docs/concepts/services-networking/ingress/), but you can also use it
-with other resources or directly in your workload.
-When using this type of Secret, the `tls.key` and the `tls.crt` key must be provided
-in the `data` (or `stringData`) field of the Secret configuration, although the API
-server doesn't actually validate the values for each key.
-
-The following YAML contains an example config for a TLS Secret:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
- name: secret-tls
-type: kubernetes.io/tls
-data:
- # the data is abbreviated in this example
- tls.crt: |
- MIIC2DCCAcCgAwIBAgIBATANBgkqh ...
- tls.key: |
- MIIEpgIBAAKCAQEA7yn3bRHQ5FHMQ ...
-```
-
-The TLS Secret type is provided for user's convenience. You can create an `Opaque`
-for credentials used for TLS server and/or client. However, using the builtin Secret
-type helps ensure the consistency of Secret format in your project; the API server
-does verify if the required keys are provided in a Secret configuration.
-
-When creating a TLS Secret using `kubectl`, you can use the `tls` subcommand
-as shown in the following example:
-
-```shell
-kubectl create secret tls my-tls-secret \
- --cert=path/to/cert/file \
- --key=path/to/key/file
-```
-
-The public/private key pair must exist before hand. The public key certificate
-for `--cert` must be DER format as per
-[Section 5.1 of RFC 7468](https://datatracker.ietf.org/doc/html/rfc7468#section-5.1),
-and must match the given private key for `--key` (PKCS #8 in DER format;
-[Section 11 of RFC 7468](https://datatracker.ietf.org/doc/html/rfc7468#section-11)).
-
-{{< note >}}
-A kubernetes.io/tls Secret stores the Base64-encoded DER data for keys and
-certificates. If you're familiar with PEM format for private keys and for certificates,
-the base64 data are the same as that format except that you omit
-the initial and the last lines that are used in PEM.
-
-For example, for a certificate, you do **not** include `--------BEGIN CERTIFICATE-----`
-and `-------END CERTIFICATE----`.
-{{< /note >}}
-
-### Bootstrap token Secrets
-
-A bootstrap token Secret can be created by explicitly specifying the Secret
-`type` to `bootstrap.kubernetes.io/token`. This type of Secret is designed for
-tokens used during the node bootstrap process. It stores tokens used to sign
-well-known ConfigMaps.
-
-A bootstrap token Secret is usually created in the `kube-system` namespace and
-named in the form `bootstrap-token-` where `` is a 6 character
-string of the token ID.
-
-As a Kubernetes manifest, a bootstrap token Secret might look like the
-following:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
- name: bootstrap-token-5emitj
- namespace: kube-system
-type: bootstrap.kubernetes.io/token
-data:
- auth-extra-groups: c3lzdGVtOmJvb3RzdHJhcHBlcnM6a3ViZWFkbTpkZWZhdWx0LW5vZGUtdG9rZW4=
- expiration: MjAyMC0wOS0xM1QwNDozOToxMFo=
- token-id: NWVtaXRq
- token-secret: a3E0Z2lodnN6emduMXAwcg==
- usage-bootstrap-authentication: dHJ1ZQ==
- usage-bootstrap-signing: dHJ1ZQ==
-```
-
-A bootstrap type Secret has the following keys specified under `data`:
-
-- `token-id`: A random 6 character string as the token identifier. Required.
-- `token-secret`: A random 16 character string as the actual token secret. Required.
-- `description`: A human-readable string that describes what the token is
- used for. Optional.
-- `expiration`: An absolute UTC time using [RFC3339](https://datatracker.ietf.org/doc/html/rfc3339) specifying when the token
- should be expired. Optional.
-- `usage-bootstrap-`: A boolean flag indicating additional usage for
- the bootstrap token.
-- `auth-extra-groups`: A comma-separated list of group names that will be
- authenticated as in addition to the `system:bootstrappers` group.
-
-The above YAML may look confusing because the values are all in base64 encoded
-strings. In fact, you can create an identical Secret using the following YAML:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
- # Note how the Secret is named
- name: bootstrap-token-5emitj
- # A bootstrap token Secret usually resides in the kube-system namespace
- namespace: kube-system
-type: bootstrap.kubernetes.io/token
-stringData:
- auth-extra-groups: "system:bootstrappers:kubeadm:default-node-token"
- expiration: "2020-09-13T04:39:10Z"
- # This token ID is used in the name
- token-id: "5emitj"
- token-secret: "kq4gihvszzgn1p0r"
- # This token can be used for authentication
- usage-bootstrap-authentication: "true"
- # and it can be used for signing
- usage-bootstrap-signing: "true"
-```
-
-## Working with Secrets
-
-### Creating a Secret
-
-There are several options to create a Secret:
-
-- [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)
-- [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/)
-- [Use the Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)
-
-#### Constraints on Secret names and data {#restriction-names-data}
-
-The name of a Secret object must be a valid
-[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
-
-You can specify the `data` and/or the `stringData` field when creating a
-configuration file for a Secret. The `data` and the `stringData` fields are optional.
-The values for all keys in the `data` field have to be base64-encoded strings.
-If the conversion to base64 string is not desirable, you can choose to specify
-the `stringData` field instead, which accepts arbitrary strings as values.
-
-The keys of `data` and `stringData` must consist of alphanumeric characters,
-`-`, `_` or `.`. All key-value pairs in the `stringData` field are internally
-merged into the `data` field. If a key appears in both the `data` and the
-`stringData` field, the value specified in the `stringData` field takes
-precedence.
-
-#### Size limit {#restriction-data-size}
-
-Individual secrets are limited to 1MiB in size. This is to discourage creation
-of very large secrets that could exhaust the API server and kubelet memory.
-However, creation of many smaller secrets could also exhaust memory. You can
-use a [resource quota](/docs/concepts/policy/resource-quotas/) to limit the
-number of Secrets (or other resources) in a namespace.
-
-### Editing a Secret
-
-You can edit an existing Secret unless it is [immutable](#secret-immutable). To
-edit a Secret, use one of the following methods:
-
-- [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/#edit-secret)
-- [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/#edit-secret)
-
-You can also edit the data in a Secret using the [Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/#edit-secret). However, this
-method creates a new `Secret` object with the edited data.
-
-Depending on how you created the Secret, as well as how the Secret is used in
-your Pods, updates to existing `Secret` objects are propagated automatically to
-Pods that use the data. For more information, refer to [Using Secrets as files from a Pod](#using-secrets-as-files-from-a-pod) section.
-
-### Using a Secret
-
-Secrets can be mounted as data volumes or exposed as
-{{< glossary_tooltip text="environment variables" term_id="container-env-variables" >}}
-to be used by a container in a Pod. Secrets can also be used by other parts of the
-system, without being directly exposed to the Pod. For example, Secrets can hold
-credentials that other parts of the system should use to interact with external
-systems on your behalf.
-
-Secret volume sources are validated to ensure that the specified object
-reference actually points to an object of type Secret. Therefore, a Secret
-needs to be created before any Pods that depend on it.
-
-If the Secret cannot be fetched (perhaps because it does not exist, or
-due to a temporary lack of connection to the API server) the kubelet
-periodically retries running that Pod. The kubelet also reports an Event
-for that Pod, including details of the problem fetching the Secret.
-
-#### Optional Secrets {#restriction-secret-must-exist}
-
-When you reference a Secret in a Pod, you can mark the Secret as _optional_,
-such as in the following example. If an optional Secret doesn't exist,
-Kubernetes ignores it.
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
- name: mypod
-spec:
- containers:
- - name: mypod
- image: redis
- volumeMounts:
- - name: foo
- mountPath: "/etc/foo"
- readOnly: true
- volumes:
- - name: foo
- secret:
- secretName: mysecret
- optional: true
-```
-
-By default, Secrets are required. None of a Pod's containers will start until
-all non-optional Secrets are available.
-
-If a Pod references a specific key in a non-optional Secret and that Secret
-does exist, but is missing the named key, the Pod fails during startup.
-
-### Using Secrets as files from a Pod {#using-secrets-as-files-from-a-pod}
-
-If you want to access data from a Secret in a Pod, one way to do that is to
-have Kubernetes make the value of that Secret be available as a file inside
-the filesystem of one or more of the Pod's containers.
-
-For instructions, refer to
-[Distribute credentials securely using Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#create-a-pod-that-has-access-to-the-secret-data-through-a-volume).
-
-When a volume contains data from a Secret, and that Secret is updated, Kubernetes tracks
-this and updates the data in the volume, using an eventually-consistent approach.
-
-{{< note >}}
-A container using a Secret as a
-[subPath](/docs/concepts/storage/volumes#using-subpath) volume mount does not receive
-automated Secret updates.
-{{< /note >}}
-
-The kubelet keeps a cache of the current keys and values for the Secrets that are used in
-volumes for pods on that node.
-You can configure the way that the kubelet detects changes from the cached values. The
-`configMapAndSecretChangeDetectionStrategy` field in the
-[kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/) controls
-which strategy the kubelet uses. The default strategy is `Watch`.
-
-Updates to Secrets can be either propagated by an API watch mechanism (the default), based on
-a cache with a defined time-to-live, or polled from the cluster API server on each kubelet
-synchronisation loop.
-
-As a result, the total delay from the moment when the Secret is updated to the moment
-when new keys are projected to the Pod can be as long as the kubelet sync period + cache
-propagation delay, where the cache propagation delay depends on the chosen cache type
-(following the same order listed in the previous paragraph, these are:
-watch propagation delay, the configured cache TTL, or zero for direct polling).
-
-### Using Secrets as environment variables
-
-To use a Secret in an {{< glossary_tooltip text="environment variable" term_id="container-env-variables" >}}
-in a Pod:
-
-1. For each container in your Pod specification, add an environment variable
- for each Secret key that you want to use to the
- `env[].valueFrom.secretKeyRef` field.
-1. Modify your image and/or command line so that the program looks for values
- in the specified environment variables.
-
-For instructions, refer to
-[Define container environment variables using Secret data](/docs/tasks/inject-data-application/distribute-credentials-secure/#define-container-environment-variables-using-secret-data).
-
-#### Invalid environment variables {#restriction-env-from-invalid}
-
-If your environment variable definitions in your Pod specification are
-considered to be invalid environment variable names, those keys aren't made
-available to your container. The Pod is allowed to start.
-
-Kubernetes adds an Event with the reason set to `InvalidVariableNames` and a
-message that lists the skipped invalid keys. The following example shows a Pod that refers to a Secret named `mysecret`, where `mysecret` contains 2 invalid keys: `1badkey` and `2alsobad`.
-
-```shell
-kubectl get events
-```
-
-The output is similar to:
-
-```
-LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON
-0s 0s 1 dapi-test-pod Pod Warning InvalidEnvironmentVariableNames kubelet, 127.0.0.1 Keys [1badkey, 2alsobad] from the EnvFrom secret default/mysecret were skipped since they are considered invalid environment variable names.
-```
-
-### Container image pull secrets {#using-imagepullsecrets}
-
-If you want to fetch container images from a private repository, you need a way for
-the kubelet on each node to authenticate to that repository. You can configure
-_image pull secrets_ to make this possible. These secrets are configured at the Pod
-level.
-
-#### Using imagePullSecrets
-
-The `imagePullSecrets` field is a list of references to secrets in the same namespace.
-You can use an `imagePullSecrets` to pass a secret that contains a Docker (or other) image registry
-password to the kubelet. The kubelet uses this information to pull a private image on behalf of your Pod.
-See the [PodSpec API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core)
-for more information about the `imagePullSecrets` field.
-
-##### Manually specifying an imagePullSecret
-
-You can learn how to specify `imagePullSecrets` from the
-[container images](/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod)
-documentation.
-
-##### Arranging for imagePullSecrets to be automatically attached
-
-You can manually create `imagePullSecrets`, and reference these from a ServiceAccount. Any Pods
-created with that ServiceAccount or created with that ServiceAccount by default, will get their
-`imagePullSecrets` field set to that of the service account.
-See [Add ImagePullSecrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account)
-for a detailed explanation of that process.
-
-### Using Secrets with static Pods {#restriction-static-pod}
-
-You cannot use ConfigMaps or Secrets with {{< glossary_tooltip text="static Pods" term_id="static-pod" >}}.
-
## Use cases
### Use case: As container environment variables {#use-case-as-container-environment-variables}
@@ -960,6 +330,637 @@ With this partitioned approach, an attacker now has to trick the application
server into doing something rather arbitrary, which may be harder than getting
it to read a file.
+### Alternatives to Secrets
+
+Rather than using a Secret to protect confidential data, you can pick from alternatives.
+
+Here are some of your options:
+
+- If your cloud-native component needs to authenticate to another application that you
+ know is running within the same Kubernetes cluster, you can use a
+ [ServiceAccount](/docs/reference/access-authn-authz/authentication/#service-account-tokens)
+ and its tokens to identify your client.
+- There are third-party tools that you can run, either within or outside your cluster,
+ that provide secrets management. For example, a service that Pods access over HTTPS,
+ that reveals a secret if the client correctly authenticates (for example, with a ServiceAccount
+ token).
+- For authentication, you can implement a custom signer for X.509 certificates, and use
+ [CertificateSigningRequests](/docs/reference/access-authn-authz/certificate-signing-requests/)
+ to let that custom signer issue certificates to Pods that need them.
+- You can use a [device plugin](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
+ to expose node-local encryption hardware to a specific Pod. For example, you can schedule
+ trusted Pods onto nodes that provide a Trusted Platform Module, configured out-of-band.
+
+You can also combine two or more of those options, including the option to use Secret objects themselves.
+
+For example: implement (or deploy) an {{< glossary_tooltip text="operator" term_id="operator-pattern" >}}
+that fetches short-lived session tokens from an external service, and then creates Secrets based
+on those short-lived session tokens. Pods running in your cluster can make use of the session tokens,
+and operator ensures they are valid. This separation means that you can run Pods that are unaware of
+the exact mechanisms for issuing and refreshing those session tokens.
+
+## Working with Secrets
+
+### Creating a Secret
+
+There are several options to create a Secret:
+
+- [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)
+- [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/)
+- [Use the Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)
+
+#### Constraints on Secret names and data {#restriction-names-data}
+
+The name of a Secret object must be a valid
+[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
+
+You can specify the `data` and/or the `stringData` field when creating a
+configuration file for a Secret. The `data` and the `stringData` fields are optional.
+The values for all keys in the `data` field have to be base64-encoded strings.
+If the conversion to base64 string is not desirable, you can choose to specify
+the `stringData` field instead, which accepts arbitrary strings as values.
+
+The keys of `data` and `stringData` must consist of alphanumeric characters,
+`-`, `_` or `.`. All key-value pairs in the `stringData` field are internally
+merged into the `data` field. If a key appears in both the `data` and the
+`stringData` field, the value specified in the `stringData` field takes
+precedence.
+
+#### Size limit {#restriction-data-size}
+
+Individual secrets are limited to 1MiB in size. This is to discourage creation
+of very large secrets that could exhaust the API server and kubelet memory.
+However, creation of many smaller secrets could also exhaust memory. You can
+use a [resource quota](/docs/concepts/policy/resource-quotas/) to limit the
+number of Secrets (or other resources) in a namespace.
+
+### Editing a Secret
+
+You can edit an existing Secret unless it is [immutable](#secret-immutable). To
+edit a Secret, use one of the following methods:
+
+* [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/#edit-secret)
+* [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/#edit-secret)
+
+You can also edit the data in a Secret using the [Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/#edit-secret). However, this
+method creates a new `Secret` object with the edited data.
+
+Depending on how you created the Secret, as well as how the Secret is used in
+your Pods, updates to existing `Secret` objects are propagated automatically to
+Pods that use the data. For more information, refer to [Using Secrets as files from a Pod](#using-secrets-as-files-from-a-pod) section.
+
+### Using a Secret
+
+Secrets can be mounted as data volumes or exposed as
+{{< glossary_tooltip text="environment variables" term_id="container-env-variables" >}}
+to be used by a container in a Pod. Secrets can also be used by other parts of the
+system, without being directly exposed to the Pod. For example, Secrets can hold
+credentials that other parts of the system should use to interact with external
+systems on your behalf.
+
+Secret volume sources are validated to ensure that the specified object
+reference actually points to an object of type Secret. Therefore, a Secret
+needs to be created before any Pods that depend on it.
+
+If the Secret cannot be fetched (perhaps because it does not exist, or
+due to a temporary lack of connection to the API server) the kubelet
+periodically retries running that Pod. The kubelet also reports an Event
+for that Pod, including details of the problem fetching the Secret.
+
+#### Optional Secrets {#restriction-secret-must-exist}
+
+When you reference a Secret in a Pod, you can mark the Secret as _optional_,
+such as in the following example. If an optional Secret doesn't exist,
+Kubernetes ignores it.
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+ name: mypod
+spec:
+ containers:
+ - name: mypod
+ image: redis
+ volumeMounts:
+ - name: foo
+ mountPath: "/etc/foo"
+ readOnly: true
+ volumes:
+ - name: foo
+ secret:
+ secretName: mysecret
+ optional: true
+```
+
+By default, Secrets are required. None of a Pod's containers will start until
+all non-optional Secrets are available.
+
+If a Pod references a specific key in a non-optional Secret and that Secret
+does exist, but is missing the named key, the Pod fails during startup.
+
+### Using Secrets as files from a Pod {#using-secrets-as-files-from-a-pod}
+
+If you want to access data from a Secret in a Pod, one way to do that is to
+have Kubernetes make the value of that Secret be available as a file inside
+the filesystem of one or more of the Pod's containers.
+
+For instructions, refer to
+[Distribute credentials securely using Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#create-a-pod-that-has-access-to-the-secret-data-through-a-volume).
+
+When a volume contains data from a Secret, and that Secret is updated, Kubernetes tracks
+this and updates the data in the volume, using an eventually-consistent approach.
+
+{{< note >}}
+A container using a Secret as a
+[subPath](/docs/concepts/storage/volumes#using-subpath) volume mount does not receive
+automated Secret updates.
+{{< /note >}}
+
+The kubelet keeps a cache of the current keys and values for the Secrets that are used in
+volumes for pods on that node.
+You can configure the way that the kubelet detects changes from the cached values. The
+`configMapAndSecretChangeDetectionStrategy` field in the
+[kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/) controls
+which strategy the kubelet uses. The default strategy is `Watch`.
+
+Updates to Secrets can be either propagated by an API watch mechanism (the default), based on
+a cache with a defined time-to-live, or polled from the cluster API server on each kubelet
+synchronisation loop.
+
+As a result, the total delay from the moment when the Secret is updated to the moment
+when new keys are projected to the Pod can be as long as the kubelet sync period + cache
+propagation delay, where the cache propagation delay depends on the chosen cache type
+(following the same order listed in the previous paragraph, these are:
+watch propagation delay, the configured cache TTL, or zero for direct polling).
+
+### Using Secrets as environment variables
+
+To use a Secret in an {{< glossary_tooltip text="environment variable" term_id="container-env-variables" >}}
+in a Pod:
+
+1. For each container in your Pod specification, add an environment variable
+ for each Secret key that you want to use to the
+ `env[].valueFrom.secretKeyRef` field.
+1. Modify your image and/or command line so that the program looks for values
+ in the specified environment variables.
+
+For instructions, refer to
+[Define container environment variables using Secret data](/docs/tasks/inject-data-application/distribute-credentials-secure/#define-container-environment-variables-using-secret-data).
+
+#### Invalid environment variables {#restriction-env-from-invalid}
+
+If your environment variable definitions in your Pod specification are
+considered to be invalid environment variable names, those keys aren't made
+available to your container. The Pod is allowed to start.
+
+Kubernetes adds an Event with the reason set to `InvalidVariableNames` and a
+message that lists the skipped invalid keys. The following example shows a Pod that refers to a Secret named `mysecret`, where `mysecret` contains 2 invalid keys: `1badkey` and `2alsobad`.
+
+```shell
+kubectl get events
+```
+
+The output is similar to:
+
+```
+LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON
+0s 0s 1 dapi-test-pod Pod Warning InvalidEnvironmentVariableNames kubelet, 127.0.0.1 Keys [1badkey, 2alsobad] from the EnvFrom secret default/mysecret were skipped since they are considered invalid environment variable names.
+```
+
+### Container image pull secrets {#using-imagepullsecrets}
+
+If you want to fetch container images from a private repository, you need a way for
+the kubelet on each node to authenticate to that repository. You can configure
+_image pull secrets_ to make this possible. These secrets are configured at the Pod
+level.
+
+#### Using imagePullSecrets
+
+The `imagePullSecrets` field is a list of references to secrets in the same namespace.
+You can use an `imagePullSecrets` to pass a secret that contains a Docker (or other) image registry
+password to the kubelet. The kubelet uses this information to pull a private image on behalf of your Pod.
+See the [PodSpec API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core)
+for more information about the `imagePullSecrets` field.
+
+##### Manually specifying an imagePullSecret
+
+You can learn how to specify `imagePullSecrets` from the
+[container images](/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod)
+documentation.
+
+##### Arranging for imagePullSecrets to be automatically attached
+
+You can manually create `imagePullSecrets`, and reference these from a ServiceAccount. Any Pods
+created with that ServiceAccount or created with that ServiceAccount by default, will get their
+`imagePullSecrets` field set to that of the service account.
+See [Add ImagePullSecrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account)
+for a detailed explanation of that process.
+
+### Using Secrets with static Pods {#restriction-static-pod}
+
+You cannot use ConfigMaps or Secrets with {{< glossary_tooltip text="static Pods" term_id="static-pod" >}}.
+
+## Types of Secret {#secret-types}
+
+When creating a Secret, you can specify its type using the `type` field of
+the [Secret](/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1/)
+resource, or certain equivalent `kubectl` command line flags (if available).
+The Secret type is used to facilitate programmatic handling of the Secret data.
+
+Kubernetes provides several built-in types for some common usage scenarios.
+These types vary in terms of the validations performed and the constraints
+Kubernetes imposes on them.
+
+| Built-in Type | Usage |
+|--------------|-------|
+| `Opaque` | arbitrary user-defined data |
+| `kubernetes.io/service-account-token` | ServiceAccount token |
+| `kubernetes.io/dockercfg` | serialized `~/.dockercfg` file |
+| `kubernetes.io/dockerconfigjson` | serialized `~/.docker/config.json` file |
+| `kubernetes.io/basic-auth` | credentials for basic authentication |
+| `kubernetes.io/ssh-auth` | credentials for SSH authentication |
+| `kubernetes.io/tls` | data for a TLS client or server |
+| `bootstrap.kubernetes.io/token` | bootstrap token data |
+
+You can define and use your own Secret type by assigning a non-empty string as the
+`type` value for a Secret object (an empty string is treated as an `Opaque` type).
+
+Kubernetes doesn't impose any constraints on the type name. However, if you
+are using one of the built-in types, you must meet all the requirements defined
+for that type.
+
+If you are defining a type of secret that's for public use, follow the convention
+and structure the secret type to have your domain name before the name, separated
+by a `/`. For example: `cloud-hosting.example.net/cloud-api-credentials`.
+
+### Opaque secrets
+
+`Opaque` is the default Secret type if omitted from a Secret configuration file.
+When you create a Secret using `kubectl`, you will use the `generic`
+subcommand to indicate an `Opaque` Secret type. For example, the following
+command creates an empty Secret of type `Opaque`.
+
+```shell
+kubectl create secret generic empty-secret
+kubectl get secret empty-secret
+```
+
+The output looks like:
+
+```
+NAME TYPE DATA AGE
+empty-secret Opaque 0 2m6s
+```
+
+The `DATA` column shows the number of data items stored in the Secret.
+In this case, `0` means you have created an empty Secret.
+
+### Service account token Secrets
+
+A `kubernetes.io/service-account-token` type of Secret is used to store a
+token credential that identifies a
+{{< glossary_tooltip text="service account" term_id="service-account" >}}.
+
+{{< note >}}
+Versions of Kubernetes before v1.22 automatically created credentials for
+accessing the Kubernetes API. This older mechanism was based on creating token
+Secrets that could then be mounted into running Pods.
+In more recent versions, including Kubernetes v{{< skew currentVersion >}}, API
+credentials are obtained directly by using the
+[TokenRequest](/docs/reference/kubernetes-api/authentication-resources/token-request-v1/)
+API, and are mounted into Pods using a
+[projected volume](/docs/reference/access-authn-authz/service-accounts-admin/#bound-service-account-token-volume).
+The tokens obtained using this method have bounded lifetimes, and are
+automatically invalidated when the Pod they are mounted into is deleted.
+
+You can still
+[manually create](/docs/tasks/configure-pod-container/configure-service-account/#manually-create-a-service-account-api-token)
+a service account token Secret; for example, if you need a token that never
+expires. However, using the
+[TokenRequest](/docs/reference/kubernetes-api/authentication-resources/token-request-v1/)
+subresource to obtain a token to access the API is recommended instead.
+You can use the
+[`kubectl create token`](/docs/reference/generated/kubectl/kubectl-commands#-em-token-em-)
+command to obtain a token from the `TokenRequest` API.
+{{< /note >}}
+
+You should only create a service account token Secret object
+if you can't use the `TokenRequest` API to obtain a token,
+and the security exposure of persisting a non-expiring token credential
+in a readable API object is acceptable to you.
+
+When using this Secret type, you need to ensure that the
+`kubernetes.io/service-account.name` annotation is set to an existing
+service account name. If you are creating both the ServiceAccount and
+the Secret objects, you should create the ServiceAccount object first.
+
+After the Secret is created, a Kubernetes {{< glossary_tooltip text="controller" term_id="controller" >}}
+fills in some other fields such as the `kubernetes.io/service-account.uid` annotation, and the
+`token` key in the `data` field, which is populated with an authentication token.
+
+The following example configuration declares a service account token Secret:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: secret-sa-sample
+ annotations:
+ kubernetes.io/service-account.name: "sa-name"
+type: kubernetes.io/service-account-token
+data:
+ # You can include additional key value pairs as you do with Opaque Secrets
+ extra: YmFyCg==
+```
+
+After creating the Secret, wait for Kubernetes to populate the `token` key in the `data` field.
+
+See the [ServiceAccount](/docs/tasks/configure-pod-container/configure-service-account/)
+documentation for more information on how service accounts work.
+You can also check the `automountServiceAccountToken` field and the
+`serviceAccountName` field of the
+[`Pod`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
+for information on referencing service account credentials from within Pods.
+
+### Docker config Secrets
+
+You can use one of the following `type` values to create a Secret to
+store the credentials for accessing a container image registry:
+
+- `kubernetes.io/dockercfg`
+- `kubernetes.io/dockerconfigjson`
+
+The `kubernetes.io/dockercfg` type is reserved to store a serialized
+`~/.dockercfg` which is the legacy format for configuring Docker command line.
+When using this Secret type, you have to ensure the Secret `data` field
+contains a `.dockercfg` key whose value is content of a `~/.dockercfg` file
+encoded in the base64 format.
+
+The `kubernetes.io/dockerconfigjson` type is designed for storing a serialized
+JSON that follows the same format rules as the `~/.docker/config.json` file
+which is a new format for `~/.dockercfg`.
+When using this Secret type, the `data` field of the Secret object must
+contain a `.dockerconfigjson` key, in which the content for the
+`~/.docker/config.json` file is provided as a base64 encoded string.
+
+Below is an example for a `kubernetes.io/dockercfg` type of Secret:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: secret-dockercfg
+type: kubernetes.io/dockercfg
+data:
+ .dockercfg: |
+ ""
+```
+
+{{< note >}}
+If you do not want to perform the base64 encoding, you can choose to use the
+`stringData` field instead.
+{{< /note >}}
+
+When you create these types of Secrets using a manifest, the API
+server checks whether the expected key exists in the `data` field, and
+it verifies if the value provided can be parsed as a valid JSON. The API
+server doesn't validate if the JSON actually is a Docker config file.
+
+When you do not have a Docker config file, or you want to use `kubectl`
+to create a Secret for accessing a container registry, you can do:
+
+```shell
+kubectl create secret docker-registry secret-tiger-docker \
+ --docker-email=tiger@acme.example \
+ --docker-username=tiger \
+ --docker-password=pass1234 \
+ --docker-server=my-registry.example:5000
+```
+
+That command creates a Secret of type `kubernetes.io/dockerconfigjson`.
+If you dump the `.data.dockerconfigjson` field from that new Secret and then
+decode it from base64:
+
+```shell
+kubectl get secret secret-tiger-docker -o jsonpath='{.data.*}' | base64 -d
+```
+
+then the output is equivalent to this JSON document (which is also a valid
+Docker configuration file):
+
+```json
+{
+ "auths": {
+ "my-registry.example:5000": {
+ "username": "tiger",
+ "password": "pass1234",
+ "email": "tiger@acme.example",
+ "auth": "dGlnZXI6cGFzczEyMzQ="
+ }
+ }
+}
+```
+
+{{< note >}}
+The `auth` value there is base64 encoded; it is obscured but not secret.
+Anyone who can read that Secret can learn the registry access bearer token.
+{{< /note >}}
+
+### Basic authentication Secret
+
+The `kubernetes.io/basic-auth` type is provided for storing credentials needed
+for basic authentication. When using this Secret type, the `data` field of the
+Secret must contain one of the following two keys:
+
+- `username`: the user name for authentication
+- `password`: the password or token for authentication
+
+Both values for the above two keys are base64 encoded strings. You can, of
+course, provide the clear text content using the `stringData` for Secret
+creation.
+
+The following manifest is an example of a basic authentication Secret:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: secret-basic-auth
+type: kubernetes.io/basic-auth
+stringData:
+ username: admin # required field for kubernetes.io/basic-auth
+ password: t0p-Secret # required field for kubernetes.io/basic-auth
+```
+
+The basic authentication Secret type is provided only for convenience.
+You can create an `Opaque` type for credentials used for basic authentication.
+However, using the defined and public Secret type (`kubernetes.io/basic-auth`) helps other
+people to understand the purpose of your Secret, and sets a convention for what key names
+to expect.
+The Kubernetes API verifies that the required keys are set for a Secret of this type.
+
+### SSH authentication secrets
+
+The builtin type `kubernetes.io/ssh-auth` is provided for storing data used in
+SSH authentication. When using this Secret type, you will have to specify a
+`ssh-privatekey` key-value pair in the `data` (or `stringData`) field
+as the SSH credential to use.
+
+The following manifest is an example of a Secret used for SSH public/private
+key authentication:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: secret-ssh-auth
+type: kubernetes.io/ssh-auth
+data:
+ # the data is abbreviated in this example
+ ssh-privatekey: |
+ MIIEpQIBAAKCAQEAulqb/Y ...
+```
+
+The SSH authentication Secret type is provided only for user's convenience.
+You could instead create an `Opaque` type Secret for credentials used for SSH authentication.
+However, using the defined and public Secret type (`kubernetes.io/ssh-auth`) helps other
+people to understand the purpose of your Secret, and sets a convention for what key names
+to expect.
+and the API server does verify if the required keys are provided in a Secret configuration.
+
+{{< caution >}}
+SSH private keys do not establish trusted communication between an SSH client and
+host server on their own. A secondary means of establishing trust is needed to
+mitigate "man in the middle" attacks, such as a `known_hosts` file added to a ConfigMap.
+{{< /caution >}}
+
+### TLS secrets
+
+Kubernetes provides a builtin Secret type `kubernetes.io/tls` for storing
+a certificate and its associated key that are typically used for TLS.
+
+One common use for TLS secrets is to configure encryption in transit for
+an [Ingress](/docs/concepts/services-networking/ingress/), but you can also use it
+with other resources or directly in your workload.
+When using this type of Secret, the `tls.key` and the `tls.crt` key must be provided
+in the `data` (or `stringData`) field of the Secret configuration, although the API
+server doesn't actually validate the values for each key.
+
+The following YAML contains an example config for a TLS Secret:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: secret-tls
+type: kubernetes.io/tls
+data:
+ # the data is abbreviated in this example
+ tls.crt: |
+ MIIC2DCCAcCgAwIBAgIBATANBgkqh ...
+ tls.key: |
+ MIIEpgIBAAKCAQEA7yn3bRHQ5FHMQ ...
+```
+
+The TLS Secret type is provided for user's convenience. You can create an `Opaque`
+for credentials used for TLS server and/or client. However, using the builtin Secret
+type helps ensure the consistency of Secret format in your project; the API server
+does verify if the required keys are provided in a Secret configuration.
+
+When creating a TLS Secret using `kubectl`, you can use the `tls` subcommand
+as shown in the following example:
+
+```shell
+kubectl create secret tls my-tls-secret \
+ --cert=path/to/cert/file \
+ --key=path/to/key/file
+```
+
+The public/private key pair must exist before hand. The public key certificate
+for `--cert` must be DER format as per
+[Section 5.1 of RFC 7468](https://datatracker.ietf.org/doc/html/rfc7468#section-5.1),
+and must match the given private key for `--key` (PKCS #8 in DER format;
+[Section 11 of RFC 7468](https://datatracker.ietf.org/doc/html/rfc7468#section-11)).
+
+{{< note >}}
+A kubernetes.io/tls Secret stores the Base64-encoded DER data for keys and
+certificates. If you're familiar with PEM format for private keys and for certificates,
+the base64 data are the same as that format except that you omit
+the initial and the last lines that are used in PEM.
+
+For example, for a certificate, you do **not** include `--------BEGIN CERTIFICATE-----`
+and `-------END CERTIFICATE----`.
+{{< /note >}}
+
+### Bootstrap token Secrets
+
+A bootstrap token Secret can be created by explicitly specifying the Secret
+`type` to `bootstrap.kubernetes.io/token`. This type of Secret is designed for
+tokens used during the node bootstrap process. It stores tokens used to sign
+well-known ConfigMaps.
+
+A bootstrap token Secret is usually created in the `kube-system` namespace and
+named in the form `bootstrap-token-` where `` is a 6 character
+string of the token ID.
+
+As a Kubernetes manifest, a bootstrap token Secret might look like the
+following:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: bootstrap-token-5emitj
+ namespace: kube-system
+type: bootstrap.kubernetes.io/token
+data:
+ auth-extra-groups: c3lzdGVtOmJvb3RzdHJhcHBlcnM6a3ViZWFkbTpkZWZhdWx0LW5vZGUtdG9rZW4=
+ expiration: MjAyMC0wOS0xM1QwNDozOToxMFo=
+ token-id: NWVtaXRq
+ token-secret: a3E0Z2lodnN6emduMXAwcg==
+ usage-bootstrap-authentication: dHJ1ZQ==
+ usage-bootstrap-signing: dHJ1ZQ==
+```
+
+A bootstrap type Secret has the following keys specified under `data`:
+
+- `token-id`: A random 6 character string as the token identifier. Required.
+- `token-secret`: A random 16 character string as the actual token secret. Required.
+- `description`: A human-readable string that describes what the token is
+ used for. Optional.
+- `expiration`: An absolute UTC time using [RFC3339](https://datatracker.ietf.org/doc/html/rfc3339) specifying when the token
+ should be expired. Optional.
+- `usage-bootstrap-`: A boolean flag indicating additional usage for
+ the bootstrap token.
+- `auth-extra-groups`: A comma-separated list of group names that will be
+ authenticated as in addition to the `system:bootstrappers` group.
+
+The above YAML may look confusing because the values are all in base64 encoded
+strings. In fact, you can create an identical Secret using the following YAML:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ # Note how the Secret is named
+ name: bootstrap-token-5emitj
+ # A bootstrap token Secret usually resides in the kube-system namespace
+ namespace: kube-system
+type: bootstrap.kubernetes.io/token
+stringData:
+ auth-extra-groups: "system:bootstrappers:kubeadm:default-node-token"
+ expiration: "2020-09-13T04:39:10Z"
+ # This token ID is used in the name
+ token-id: "5emitj"
+ token-secret: "kq4gihvszzgn1p0r"
+ # This token can be used for authentication
+ usage-bootstrap-authentication: "true"
+ # and it can be used for signing
+ usage-bootstrap-signing: "true"
+```
+
+
## Immutable Secrets {#secret-immutable}
{{< feature-state for_k8s_version="v1.21" state="stable" >}}
From 5bfb353a4e1a9f0611aa25d23aaae0abc27632b4 Mon Sep 17 00:00:00 2001
From: Shannon Kularathna
Date: Fri, 7 Jul 2023 19:48:14 +0000
Subject: [PATCH 086/446] Convert env variables use case and SSH key use case
into bullets with links
- Link to the actual task topics
- Remove the list of uses for secrets that link to anchors on page and replace with links to tasks
---
.../en/docs/concepts/configuration/secret.md | 75 +------------------
1 file changed, 4 insertions(+), 71 deletions(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index b24c02ac79..4df55caadf 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -55,83 +55,16 @@ See [Information security for Secrets](#information-security-for-secrets) for mo
## Uses for Secrets
-There are three main ways for a Pod to use a Secret:
+You can use Secrets for purposes such as the following:
-- As [files](#using-secrets-as-files-from-a-pod) in a
- {{< glossary_tooltip text="volume" term_id="volume" >}} mounted on one or more of
- its containers.
-- As [container environment variable](#using-secrets-as-environment-variables).
-- By the [kubelet when pulling images](#using-imagepullsecrets) for the Pod.
+- [Set environment variables for a container](/docs/tasks/inject-data-application/distribute-credentials-secure/#define-container-environment-variables-using-secret-data).
+- [Provide credentials such as SSH keys or passwords to Pods](/docs/tasks/inject-data-application/distribute-credentials-secure/#provide-prod-test-creds).
+- [Allow the kubelet to pull container images from private registries](/docs/tasks/configure-pod-container/pull-image-private-registry/).
The Kubernetes control plane also uses Secrets; for example,
[bootstrap token Secrets](#bootstrap-token-secrets) are a mechanism to
help automate node registration.
-## Use cases
-
-### Use case: As container environment variables {#use-case-as-container-environment-variables}
-
-You can create a Secret and use it to
-[set environment variables for a container](/docs/tasks/inject-data-application/distribute-credentials-secure/#define-container-environment-variables-using-secret-data).
-
-### Use case: Pod with SSH keys
-
-Create a Secret containing some SSH keys:
-
-```shell
-kubectl create secret generic ssh-key-secret --from-file=ssh-privatekey=/path/to/.ssh/id_rsa --from-file=ssh-publickey=/path/to/.ssh/id_rsa.pub
-```
-
-The output is similar to:
-
-```
-secret "ssh-key-secret" created
-```
-
-You can also create a `kustomization.yaml` with a `secretGenerator` field containing ssh keys.
-
-{{< caution >}}
-Think carefully before sending your own SSH keys: other users of the cluster may have access
-to the Secret.
-
-You could instead create an SSH private key representing a service identity that you want to be
-accessible to all the users with whom you share the Kubernetes cluster, and that you can revoke
-if the credentials are compromised.
-{{< /caution >}}
-
-Now you can create a Pod which references the secret with the SSH key and
-consumes it in a volume:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
- name: secret-test-pod
- labels:
- name: secret-test
-spec:
- volumes:
- - name: secret-volume
- secret:
- secretName: ssh-key-secret
- containers:
- - name: ssh-test-container
- image: mySshImage
- volumeMounts:
- - name: secret-volume
- readOnly: true
- mountPath: "/etc/secret-volume"
-```
-
-When the container's command runs, the pieces of the key will be available in:
-
-```
-/etc/secret-volume/ssh-publickey
-/etc/secret-volume/ssh-privatekey
-```
-
-The container is then free to use the secret data to establish an SSH connection.
-
### Use case: Pods with prod / test credentials
This example illustrates a Pod which consumes a secret containing production credentials and
From bbb9572eff8423f7de50eb09085872e6f8ef79bc Mon Sep 17 00:00:00 2001
From: Shannon Kularathna
Date: Fri, 7 Jul 2023 19:49:05 +0000
Subject: [PATCH 087/446] Move prod-test use case to task page - no content
changes
---
.../en/docs/concepts/configuration/secret.md | 137 ------------------
.../distribute-credentials-secure.md | 137 ++++++++++++++++++
2 files changed, 137 insertions(+), 137 deletions(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index 4df55caadf..cd6ac0c520 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -65,143 +65,6 @@ The Kubernetes control plane also uses Secrets; for example,
[bootstrap token Secrets](#bootstrap-token-secrets) are a mechanism to
help automate node registration.
-### Use case: Pods with prod / test credentials
-
-This example illustrates a Pod which consumes a secret containing production credentials and
-another Pod which consumes a secret with test environment credentials.
-
-You can create a `kustomization.yaml` with a `secretGenerator` field or run
-`kubectl create secret`.
-
-```shell
-kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
-```
-
-The output is similar to:
-
-```
-secret "prod-db-secret" created
-```
-
-You can also create a secret for test environment credentials.
-
-```shell
-kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
-```
-
-The output is similar to:
-
-```
-secret "test-db-secret" created
-```
-
-{{< note >}}
-Special characters such as `$`, `\`, `*`, `=`, and `!` will be interpreted by your
-[shell](https://en.wikipedia.org/wiki/Shell_(computing)) and require escaping.
-
-In most shells, the easiest way to escape the password is to surround it with single quotes (`'`).
-For example, if your actual password is `S!B\*d$zDsb=`, you should execute the command this way:
-
-```shell
-kubectl create secret generic dev-db-secret --from-literal=username=devuser --from-literal=password='S!B\*d$zDsb='
-```
-
-You do not need to escape special characters in passwords from files (`--from-file`).
-{{< /note >}}
-
-Now make the Pods:
-
-```shell
-cat < pod.yaml
-apiVersion: v1
-kind: List
-items:
-- kind: Pod
- apiVersion: v1
- metadata:
- name: prod-db-client-pod
- labels:
- name: prod-db-client
- spec:
- volumes:
- - name: secret-volume
- secret:
- secretName: prod-db-secret
- containers:
- - name: db-client-container
- image: myClientImage
- volumeMounts:
- - name: secret-volume
- readOnly: true
- mountPath: "/etc/secret-volume"
-- kind: Pod
- apiVersion: v1
- metadata:
- name: test-db-client-pod
- labels:
- name: test-db-client
- spec:
- volumes:
- - name: secret-volume
- secret:
- secretName: test-db-secret
- containers:
- - name: db-client-container
- image: myClientImage
- volumeMounts:
- - name: secret-volume
- readOnly: true
- mountPath: "/etc/secret-volume"
-EOF
-```
-
-Add the pods to the same `kustomization.yaml`:
-
-```shell
-cat <> kustomization.yaml
-resources:
-- pod.yaml
-EOF
-```
-
-Apply all those objects on the API server by running:
-
-```shell
-kubectl apply -k .
-```
-
-Both containers will have the following files present on their filesystems with the values
-for each container's environment:
-
-```
-/etc/secret-volume/username
-/etc/secret-volume/password
-```
-
-Note how the specs for the two Pods differ only in one field; this facilitates
-creating Pods with different capabilities from a common Pod template.
-
-You could further simplify the base Pod specification by using two service accounts:
-
-1. `prod-user` with the `prod-db-secret`
-1. `test-user` with the `test-db-secret`
-
-The Pod specification is shortened to:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
- name: prod-db-client-pod
- labels:
- name: prod-db-client
-spec:
- serviceAccount: prod-db-client
- containers:
- - name: db-client-container
- image: myClientImage
-```
-
### Use case: dotfiles in a secret volume
You can make your data "hidden" by defining a key that begins with a dot.
diff --git a/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md b/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
index aa8efd5e13..500e405f2f 100644
--- a/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
+++ b/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
@@ -335,6 +335,143 @@ This functionality is available in Kubernetes v1.6 and later.
password: 39528$vdg7Jb
```
+### Use case: Pods with prod / test credentials
+
+This example illustrates a Pod which consumes a secret containing production credentials and
+another Pod which consumes a secret with test environment credentials.
+
+You can create a `kustomization.yaml` with a `secretGenerator` field or run
+`kubectl create secret`.
+
+```shell
+kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
+```
+
+The output is similar to:
+
+```
+secret "prod-db-secret" created
+```
+
+You can also create a secret for test environment credentials.
+
+```shell
+kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
+```
+
+The output is similar to:
+
+```
+secret "test-db-secret" created
+```
+
+{{< note >}}
+Special characters such as `$`, `\`, `*`, `=`, and `!` will be interpreted by your
+[shell](https://en.wikipedia.org/wiki/Shell_(computing)) and require escaping.
+
+In most shells, the easiest way to escape the password is to surround it with single quotes (`'`).
+For example, if your actual password is `S!B\*d$zDsb=`, you should execute the command this way:
+
+```shell
+kubectl create secret generic dev-db-secret --from-literal=username=devuser --from-literal=password='S!B\*d$zDsb='
+```
+
+You do not need to escape special characters in passwords from files (`--from-file`).
+{{< /note >}}
+
+Now make the Pods:
+
+```shell
+cat < pod.yaml
+apiVersion: v1
+kind: List
+items:
+- kind: Pod
+ apiVersion: v1
+ metadata:
+ name: prod-db-client-pod
+ labels:
+ name: prod-db-client
+ spec:
+ volumes:
+ - name: secret-volume
+ secret:
+ secretName: prod-db-secret
+ containers:
+ - name: db-client-container
+ image: myClientImage
+ volumeMounts:
+ - name: secret-volume
+ readOnly: true
+ mountPath: "/etc/secret-volume"
+- kind: Pod
+ apiVersion: v1
+ metadata:
+ name: test-db-client-pod
+ labels:
+ name: test-db-client
+ spec:
+ volumes:
+ - name: secret-volume
+ secret:
+ secretName: test-db-secret
+ containers:
+ - name: db-client-container
+ image: myClientImage
+ volumeMounts:
+ - name: secret-volume
+ readOnly: true
+ mountPath: "/etc/secret-volume"
+EOF
+```
+
+Add the pods to the same `kustomization.yaml`:
+
+```shell
+cat <> kustomization.yaml
+resources:
+- pod.yaml
+EOF
+```
+
+Apply all those objects on the API server by running:
+
+```shell
+kubectl apply -k .
+```
+
+Both containers will have the following files present on their filesystems with the values
+for each container's environment:
+
+```
+/etc/secret-volume/username
+/etc/secret-volume/password
+```
+
+Note how the specs for the two Pods differ only in one field; this facilitates
+creating Pods with different capabilities from a common Pod template.
+
+You could further simplify the base Pod specification by using two service accounts:
+
+1. `prod-user` with the `prod-db-secret`
+1. `test-user` with the `test-db-secret`
+
+The Pod specification is shortened to:
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+ name: prod-db-client-pod
+ labels:
+ name: prod-db-client
+spec:
+ serviceAccount: prod-db-client
+ containers:
+ - name: db-client-container
+ image: myClientImage
+```
+
### References
- [Secret](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#secret-v1-core)
From 9bdbe903ee21e403109f1b3315fffac1538b58f0 Mon Sep 17 00:00:00 2001
From: Shannon Kularathna
Date: Fri, 7 Jul 2023 19:58:17 +0000
Subject: [PATCH 088/446] Improve the prod/test task section
- Use numbered lists
- Remove kustomization instructions as they were not comprehensive
- Move the note pointing out specs are sharing a template to right under the specs
- Make the step wording active voice
---
.../en/docs/concepts/configuration/secret.md | 427 +++++++++---------
.../distribute-credentials-secure.md | 164 ++++---
2 files changed, 289 insertions(+), 302 deletions(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index cd6ac0c520..7ffe4d731d 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -155,208 +155,6 @@ on those short-lived session tokens. Pods running in your cluster can make use o
and operator ensures they are valid. This separation means that you can run Pods that are unaware of
the exact mechanisms for issuing and refreshing those session tokens.
-## Working with Secrets
-
-### Creating a Secret
-
-There are several options to create a Secret:
-
-- [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)
-- [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/)
-- [Use the Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)
-
-#### Constraints on Secret names and data {#restriction-names-data}
-
-The name of a Secret object must be a valid
-[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
-
-You can specify the `data` and/or the `stringData` field when creating a
-configuration file for a Secret. The `data` and the `stringData` fields are optional.
-The values for all keys in the `data` field have to be base64-encoded strings.
-If the conversion to base64 string is not desirable, you can choose to specify
-the `stringData` field instead, which accepts arbitrary strings as values.
-
-The keys of `data` and `stringData` must consist of alphanumeric characters,
-`-`, `_` or `.`. All key-value pairs in the `stringData` field are internally
-merged into the `data` field. If a key appears in both the `data` and the
-`stringData` field, the value specified in the `stringData` field takes
-precedence.
-
-#### Size limit {#restriction-data-size}
-
-Individual secrets are limited to 1MiB in size. This is to discourage creation
-of very large secrets that could exhaust the API server and kubelet memory.
-However, creation of many smaller secrets could also exhaust memory. You can
-use a [resource quota](/docs/concepts/policy/resource-quotas/) to limit the
-number of Secrets (or other resources) in a namespace.
-
-### Editing a Secret
-
-You can edit an existing Secret unless it is [immutable](#secret-immutable). To
-edit a Secret, use one of the following methods:
-
-* [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/#edit-secret)
-* [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/#edit-secret)
-
-You can also edit the data in a Secret using the [Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/#edit-secret). However, this
-method creates a new `Secret` object with the edited data.
-
-Depending on how you created the Secret, as well as how the Secret is used in
-your Pods, updates to existing `Secret` objects are propagated automatically to
-Pods that use the data. For more information, refer to [Using Secrets as files from a Pod](#using-secrets-as-files-from-a-pod) section.
-
-### Using a Secret
-
-Secrets can be mounted as data volumes or exposed as
-{{< glossary_tooltip text="environment variables" term_id="container-env-variables" >}}
-to be used by a container in a Pod. Secrets can also be used by other parts of the
-system, without being directly exposed to the Pod. For example, Secrets can hold
-credentials that other parts of the system should use to interact with external
-systems on your behalf.
-
-Secret volume sources are validated to ensure that the specified object
-reference actually points to an object of type Secret. Therefore, a Secret
-needs to be created before any Pods that depend on it.
-
-If the Secret cannot be fetched (perhaps because it does not exist, or
-due to a temporary lack of connection to the API server) the kubelet
-periodically retries running that Pod. The kubelet also reports an Event
-for that Pod, including details of the problem fetching the Secret.
-
-#### Optional Secrets {#restriction-secret-must-exist}
-
-When you reference a Secret in a Pod, you can mark the Secret as _optional_,
-such as in the following example. If an optional Secret doesn't exist,
-Kubernetes ignores it.
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
- name: mypod
-spec:
- containers:
- - name: mypod
- image: redis
- volumeMounts:
- - name: foo
- mountPath: "/etc/foo"
- readOnly: true
- volumes:
- - name: foo
- secret:
- secretName: mysecret
- optional: true
-```
-
-By default, Secrets are required. None of a Pod's containers will start until
-all non-optional Secrets are available.
-
-If a Pod references a specific key in a non-optional Secret and that Secret
-does exist, but is missing the named key, the Pod fails during startup.
-
-### Using Secrets as files from a Pod {#using-secrets-as-files-from-a-pod}
-
-If you want to access data from a Secret in a Pod, one way to do that is to
-have Kubernetes make the value of that Secret be available as a file inside
-the filesystem of one or more of the Pod's containers.
-
-For instructions, refer to
-[Distribute credentials securely using Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#create-a-pod-that-has-access-to-the-secret-data-through-a-volume).
-
-When a volume contains data from a Secret, and that Secret is updated, Kubernetes tracks
-this and updates the data in the volume, using an eventually-consistent approach.
-
-{{< note >}}
-A container using a Secret as a
-[subPath](/docs/concepts/storage/volumes#using-subpath) volume mount does not receive
-automated Secret updates.
-{{< /note >}}
-
-The kubelet keeps a cache of the current keys and values for the Secrets that are used in
-volumes for pods on that node.
-You can configure the way that the kubelet detects changes from the cached values. The
-`configMapAndSecretChangeDetectionStrategy` field in the
-[kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/) controls
-which strategy the kubelet uses. The default strategy is `Watch`.
-
-Updates to Secrets can be either propagated by an API watch mechanism (the default), based on
-a cache with a defined time-to-live, or polled from the cluster API server on each kubelet
-synchronisation loop.
-
-As a result, the total delay from the moment when the Secret is updated to the moment
-when new keys are projected to the Pod can be as long as the kubelet sync period + cache
-propagation delay, where the cache propagation delay depends on the chosen cache type
-(following the same order listed in the previous paragraph, these are:
-watch propagation delay, the configured cache TTL, or zero for direct polling).
-
-### Using Secrets as environment variables
-
-To use a Secret in an {{< glossary_tooltip text="environment variable" term_id="container-env-variables" >}}
-in a Pod:
-
-1. For each container in your Pod specification, add an environment variable
- for each Secret key that you want to use to the
- `env[].valueFrom.secretKeyRef` field.
-1. Modify your image and/or command line so that the program looks for values
- in the specified environment variables.
-
-For instructions, refer to
-[Define container environment variables using Secret data](/docs/tasks/inject-data-application/distribute-credentials-secure/#define-container-environment-variables-using-secret-data).
-
-#### Invalid environment variables {#restriction-env-from-invalid}
-
-If your environment variable definitions in your Pod specification are
-considered to be invalid environment variable names, those keys aren't made
-available to your container. The Pod is allowed to start.
-
-Kubernetes adds an Event with the reason set to `InvalidVariableNames` and a
-message that lists the skipped invalid keys. The following example shows a Pod that refers to a Secret named `mysecret`, where `mysecret` contains 2 invalid keys: `1badkey` and `2alsobad`.
-
-```shell
-kubectl get events
-```
-
-The output is similar to:
-
-```
-LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON
-0s 0s 1 dapi-test-pod Pod Warning InvalidEnvironmentVariableNames kubelet, 127.0.0.1 Keys [1badkey, 2alsobad] from the EnvFrom secret default/mysecret were skipped since they are considered invalid environment variable names.
-```
-
-### Container image pull secrets {#using-imagepullsecrets}
-
-If you want to fetch container images from a private repository, you need a way for
-the kubelet on each node to authenticate to that repository. You can configure
-_image pull secrets_ to make this possible. These secrets are configured at the Pod
-level.
-
-#### Using imagePullSecrets
-
-The `imagePullSecrets` field is a list of references to secrets in the same namespace.
-You can use an `imagePullSecrets` to pass a secret that contains a Docker (or other) image registry
-password to the kubelet. The kubelet uses this information to pull a private image on behalf of your Pod.
-See the [PodSpec API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core)
-for more information about the `imagePullSecrets` field.
-
-##### Manually specifying an imagePullSecret
-
-You can learn how to specify `imagePullSecrets` from the
-[container images](/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod)
-documentation.
-
-##### Arranging for imagePullSecrets to be automatically attached
-
-You can manually create `imagePullSecrets`, and reference these from a ServiceAccount. Any Pods
-created with that ServiceAccount or created with that ServiceAccount by default, will get their
-`imagePullSecrets` field set to that of the service account.
-See [Add ImagePullSecrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account)
-for a detailed explanation of that process.
-
-### Using Secrets with static Pods {#restriction-static-pod}
-
-You cannot use ConfigMaps or Secrets with {{< glossary_tooltip text="static Pods" term_id="static-pod" >}}.
-
## Types of Secret {#secret-types}
When creating a Secret, you can specify its type using the `type` field of
@@ -368,16 +166,16 @@ Kubernetes provides several built-in types for some common usage scenarios.
These types vary in terms of the validations performed and the constraints
Kubernetes imposes on them.
-| Built-in Type | Usage |
-|--------------|-------|
-| `Opaque` | arbitrary user-defined data |
-| `kubernetes.io/service-account-token` | ServiceAccount token |
-| `kubernetes.io/dockercfg` | serialized `~/.dockercfg` file |
-| `kubernetes.io/dockerconfigjson` | serialized `~/.docker/config.json` file |
-| `kubernetes.io/basic-auth` | credentials for basic authentication |
-| `kubernetes.io/ssh-auth` | credentials for SSH authentication |
-| `kubernetes.io/tls` | data for a TLS client or server |
-| `bootstrap.kubernetes.io/token` | bootstrap token data |
+| Built-in Type | Usage |
+| ------------------------------------- |---------------------------------------- |
+| `Opaque` | arbitrary user-defined data |
+| `kubernetes.io/service-account-token` | ServiceAccount token |
+| `kubernetes.io/dockercfg` | serialized `~/.dockercfg` file |
+| `kubernetes.io/dockerconfigjson` | serialized `~/.docker/config.json` file |
+| `kubernetes.io/basic-auth` | credentials for basic authentication |
+| `kubernetes.io/ssh-auth` | credentials for SSH authentication |
+| `kubernetes.io/tls` | data for a TLS client or server |
+| `bootstrap.kubernetes.io/token` | bootstrap token data |
You can define and use your own Secret type by assigning a non-empty string as the
`type` value for a Secret object (an empty string is treated as an `Opaque` type).
@@ -585,7 +383,7 @@ metadata:
name: secret-basic-auth
type: kubernetes.io/basic-auth
stringData:
- username: admin # required field for kubernetes.io/basic-auth
+ username: admin # required field for kubernetes.io/basic-auth
password: t0p-Secret # required field for kubernetes.io/basic-auth
```
@@ -615,7 +413,7 @@ type: kubernetes.io/ssh-auth
data:
# the data is abbreviated in this example
ssh-privatekey: |
- MIIEpQIBAAKCAQEAulqb/Y ...
+ MIIEpQIBAAKCAQEAulqb/Y ...
```
The SSH authentication Secret type is provided only for user's convenience.
@@ -756,6 +554,207 @@ stringData:
usage-bootstrap-signing: "true"
```
+## Working with Secrets
+
+### Creating a Secret
+
+There are several options to create a Secret:
+
+- [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)
+- [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/)
+- [Use the Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)
+
+#### Constraints on Secret names and data {#restriction-names-data}
+
+The name of a Secret object must be a valid
+[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
+
+You can specify the `data` and/or the `stringData` field when creating a
+configuration file for a Secret. The `data` and the `stringData` fields are optional.
+The values for all keys in the `data` field have to be base64-encoded strings.
+If the conversion to base64 string is not desirable, you can choose to specify
+the `stringData` field instead, which accepts arbitrary strings as values.
+
+The keys of `data` and `stringData` must consist of alphanumeric characters,
+`-`, `_` or `.`. All key-value pairs in the `stringData` field are internally
+merged into the `data` field. If a key appears in both the `data` and the
+`stringData` field, the value specified in the `stringData` field takes
+precedence.
+
+#### Size limit {#restriction-data-size}
+
+Individual secrets are limited to 1MiB in size. This is to discourage creation
+of very large secrets that could exhaust the API server and kubelet memory.
+However, creation of many smaller secrets could also exhaust memory. You can
+use a [resource quota](/docs/concepts/policy/resource-quotas/) to limit the
+number of Secrets (or other resources) in a namespace.
+
+### Editing a Secret
+
+You can edit an existing Secret unless it is [immutable](#secret-immutable). To
+edit a Secret, use one of the following methods:
+
+- [Use `kubectl`](/docs/tasks/configmap-secret/managing-secret-using-kubectl/#edit-secret)
+- [Use a configuration file](/docs/tasks/configmap-secret/managing-secret-using-config-file/#edit-secret)
+
+You can also edit the data in a Secret using the [Kustomize tool](/docs/tasks/configmap-secret/managing-secret-using-kustomize/#edit-secret). However, this
+method creates a new `Secret` object with the edited data.
+
+Depending on how you created the Secret, as well as how the Secret is used in
+your Pods, updates to existing `Secret` objects are propagated automatically to
+Pods that use the data. For more information, refer to [Using Secrets as files from a Pod](#using-secrets-as-files-from-a-pod) section.
+
+### Using a Secret
+
+Secrets can be mounted as data volumes or exposed as
+{{< glossary_tooltip text="environment variables" term_id="container-env-variables" >}}
+to be used by a container in a Pod. Secrets can also be used by other parts of the
+system, without being directly exposed to the Pod. For example, Secrets can hold
+credentials that other parts of the system should use to interact with external
+systems on your behalf.
+
+Secret volume sources are validated to ensure that the specified object
+reference actually points to an object of type Secret. Therefore, a Secret
+needs to be created before any Pods that depend on it.
+
+If the Secret cannot be fetched (perhaps because it does not exist, or
+due to a temporary lack of connection to the API server) the kubelet
+periodically retries running that Pod. The kubelet also reports an Event
+for that Pod, including details of the problem fetching the Secret.
+
+#### Optional Secrets {#restriction-secret-must-exist}
+
+When you reference a Secret in a Pod, you can mark the Secret as _optional_,
+such as in the following example. If an optional Secret doesn't exist,
+Kubernetes ignores it.
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+ name: mypod
+spec:
+ containers:
+ - name: mypod
+ image: redis
+ volumeMounts:
+ - name: foo
+ mountPath: "/etc/foo"
+ readOnly: true
+ volumes:
+ - name: foo
+ secret:
+ secretName: mysecret
+ optional: true
+```
+
+By default, Secrets are required. None of a Pod's containers will start until
+all non-optional Secrets are available.
+
+If a Pod references a specific key in a non-optional Secret and that Secret
+does exist, but is missing the named key, the Pod fails during startup.
+
+### Using Secrets as files from a Pod {#using-secrets-as-files-from-a-pod}
+
+If you want to access data from a Secret in a Pod, one way to do that is to
+have Kubernetes make the value of that Secret be available as a file inside
+the filesystem of one or more of the Pod's containers.
+
+For instructions, refer to
+[Distribute credentials securely using Secrets](/docs/tasks/inject-data-application/distribute-credentials-secure/#create-a-pod-that-has-access-to-the-secret-data-through-a-volume).
+
+When a volume contains data from a Secret, and that Secret is updated, Kubernetes tracks
+this and updates the data in the volume, using an eventually-consistent approach.
+
+{{< note >}}
+A container using a Secret as a
+[subPath](/docs/concepts/storage/volumes#using-subpath) volume mount does not receive
+automated Secret updates.
+{{< /note >}}
+
+The kubelet keeps a cache of the current keys and values for the Secrets that are used in
+volumes for pods on that node.
+You can configure the way that the kubelet detects changes from the cached values. The
+`configMapAndSecretChangeDetectionStrategy` field in the
+[kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/) controls
+which strategy the kubelet uses. The default strategy is `Watch`.
+
+Updates to Secrets can be either propagated by an API watch mechanism (the default), based on
+a cache with a defined time-to-live, or polled from the cluster API server on each kubelet
+synchronisation loop.
+
+As a result, the total delay from the moment when the Secret is updated to the moment
+when new keys are projected to the Pod can be as long as the kubelet sync period + cache
+propagation delay, where the cache propagation delay depends on the chosen cache type
+(following the same order listed in the previous paragraph, these are:
+watch propagation delay, the configured cache TTL, or zero for direct polling).
+
+### Using Secrets as environment variables
+
+To use a Secret in an {{< glossary_tooltip text="environment variable" term_id="container-env-variables" >}}
+in a Pod:
+
+1. For each container in your Pod specification, add an environment variable
+ for each Secret key that you want to use to the
+ `env[].valueFrom.secretKeyRef` field.
+1. Modify your image and/or command line so that the program looks for values
+ in the specified environment variables.
+
+For instructions, refer to
+[Define container environment variables using Secret data](/docs/tasks/inject-data-application/distribute-credentials-secure/#define-container-environment-variables-using-secret-data).
+
+#### Invalid environment variables {#restriction-env-from-invalid}
+
+If your environment variable definitions in your Pod specification are
+considered to be invalid environment variable names, those keys aren't made
+available to your container. The Pod is allowed to start.
+
+Kubernetes adds an Event with the reason set to `InvalidVariableNames` and a
+message that lists the skipped invalid keys. The following example shows a Pod that refers to a Secret named `mysecret`, where `mysecret` contains 2 invalid keys: `1badkey` and `2alsobad`.
+
+```shell
+kubectl get events
+```
+
+The output is similar to:
+
+```
+LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON
+0s 0s 1 dapi-test-pod Pod Warning InvalidEnvironmentVariableNames kubelet, 127.0.0.1 Keys [1badkey, 2alsobad] from the EnvFrom secret default/mysecret were skipped since they are considered invalid environment variable names.
+```
+
+### Container image pull secrets {#using-imagepullsecrets}
+
+If you want to fetch container images from a private repository, you need a way for
+the kubelet on each node to authenticate to that repository. You can configure
+_image pull secrets_ to make this possible. These secrets are configured at the Pod
+level.
+
+#### Using imagePullSecrets
+
+The `imagePullSecrets` field is a list of references to secrets in the same namespace.
+You can use an `imagePullSecrets` to pass a secret that contains a Docker (or other) image registry
+password to the kubelet. The kubelet uses this information to pull a private image on behalf of your Pod.
+See the [PodSpec API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core)
+for more information about the `imagePullSecrets` field.
+
+##### Manually specifying an imagePullSecret
+
+You can learn how to specify `imagePullSecrets` from the
+[container images](/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod)
+documentation.
+
+##### Arranging for imagePullSecrets to be automatically attached
+
+You can manually create `imagePullSecrets`, and reference these from a ServiceAccount. Any Pods
+created with that ServiceAccount or created with that ServiceAccount by default, will get their
+`imagePullSecrets` field set to that of the service account.
+See [Add ImagePullSecrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account)
+for a detailed explanation of that process.
+
+### Using Secrets with static Pods {#restriction-static-pod}
+
+You cannot use ConfigMaps or Secrets with {{< glossary_tooltip text="static Pods" term_id="static-pod" >}}.
## Immutable Secrets {#secret-immutable}
diff --git a/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md b/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
index 500e405f2f..bb1114486c 100644
--- a/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
+++ b/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
@@ -335,110 +335,101 @@ This functionality is available in Kubernetes v1.6 and later.
password: 39528$vdg7Jb
```
-### Use case: Pods with prod / test credentials
+## Example: Provide prod/test credentials to Pods using Secrets {#provide-prod-test-creds}
This example illustrates a Pod which consumes a secret containing production credentials and
another Pod which consumes a secret with test environment credentials.
-You can create a `kustomization.yaml` with a `secretGenerator` field or run
-`kubectl create secret`.
+1. Create a secret for prod environment credentials:
-```shell
-kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
-```
+ ```shell
+ kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
+ ```
-The output is similar to:
+ The output is similar to:
-```
-secret "prod-db-secret" created
-```
+ ```
+ secret "prod-db-secret" created
+ ```
-You can also create a secret for test environment credentials.
+1. Create a secret for test environment credentials.
-```shell
-kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
-```
+ ```shell
+ kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
+ ```
-The output is similar to:
+ The output is similar to:
-```
-secret "test-db-secret" created
-```
+ ```
+ secret "test-db-secret" created
+ ```
-{{< note >}}
-Special characters such as `$`, `\`, `*`, `=`, and `!` will be interpreted by your
-[shell](https://en.wikipedia.org/wiki/Shell_(computing)) and require escaping.
+ {{< note >}}
+ Special characters such as `$`, `\`, `*`, `=`, and `!` will be interpreted by your
+ [shell](https://en.wikipedia.org/wiki/Shell_(computing)) and require escaping.
-In most shells, the easiest way to escape the password is to surround it with single quotes (`'`).
-For example, if your actual password is `S!B\*d$zDsb=`, you should execute the command this way:
+ In most shells, the easiest way to escape the password is to surround it with single quotes (`'`).
+ For example, if your actual password is `S!B\*d$zDsb=`, you should execute the command as follows:
-```shell
-kubectl create secret generic dev-db-secret --from-literal=username=devuser --from-literal=password='S!B\*d$zDsb='
-```
+ ```shell
+ kubectl create secret generic dev-db-secret --from-literal=username=devuser --from-literal=password='S!B\*d$zDsb='
+ ```
-You do not need to escape special characters in passwords from files (`--from-file`).
-{{< /note >}}
+ You do not need to escape special characters in passwords from files (`--from-file`).
+ {{< /note >}}
-Now make the Pods:
+1. Create the Pod manifests:
-```shell
-cat < pod.yaml
-apiVersion: v1
-kind: List
-items:
-- kind: Pod
- apiVersion: v1
- metadata:
- name: prod-db-client-pod
- labels:
- name: prod-db-client
- spec:
- volumes:
- - name: secret-volume
- secret:
- secretName: prod-db-secret
- containers:
- - name: db-client-container
- image: myClientImage
- volumeMounts:
- - name: secret-volume
- readOnly: true
- mountPath: "/etc/secret-volume"
-- kind: Pod
- apiVersion: v1
- metadata:
- name: test-db-client-pod
- labels:
- name: test-db-client
- spec:
- volumes:
- - name: secret-volume
- secret:
- secretName: test-db-secret
- containers:
- - name: db-client-container
- image: myClientImage
- volumeMounts:
- - name: secret-volume
- readOnly: true
- mountPath: "/etc/secret-volume"
-EOF
-```
+ ```shell
+ cat < pod.yaml
+ apiVersion: v1
+ kind: List
+ items:
+ - kind: Pod
+ apiVersion: v1
+ metadata:
+ name: prod-db-client-pod
+ labels:
+ name: prod-db-client
+ spec:
+ volumes:
+ - name: secret-volume
+ secret:
+ secretName: prod-db-secret
+ containers:
+ - name: db-client-container
+ image: myClientImage
+ volumeMounts:
+ - name: secret-volume
+ readOnly: true
+ mountPath: "/etc/secret-volume"
+ - kind: Pod
+ apiVersion: v1
+ metadata:
+ name: test-db-client-pod
+ labels:
+ name: test-db-client
+ spec:
+ volumes:
+ - name: secret-volume
+ secret:
+ secretName: test-db-secret
+ containers:
+ - name: db-client-container
+ image: myClientImage
+ volumeMounts:
+ - name: secret-volume
+ readOnly: true
+ mountPath: "/etc/secret-volume"
+ EOF
+ ```
+ Note how the specs for the two Pods differ only in one field; this facilitates creating Pods with different capabilities from a common Pod template.
-Add the pods to the same `kustomization.yaml`:
+1. Apply all those objects on the API server by running:
-```shell
-cat <> kustomization.yaml
-resources:
-- pod.yaml
-EOF
-```
-
-Apply all those objects on the API server by running:
-
-```shell
-kubectl apply -k .
-```
+ ```shell
+ kubectl create -f pod.yaml
+ ```
Both containers will have the following files present on their filesystems with the values
for each container's environment:
@@ -448,9 +439,6 @@ for each container's environment:
/etc/secret-volume/password
```
-Note how the specs for the two Pods differ only in one field; this facilitates
-creating Pods with different capabilities from a common Pod template.
-
You could further simplify the base Pod specification by using two service accounts:
1. `prod-user` with the `prod-db-secret`
From a9db7877a8ec15dc34be208c398e236e34e854ab Mon Sep 17 00:00:00 2001
From: Shannon Kularathna
Date: Wed, 26 Jul 2023 21:18:54 +0000
Subject: [PATCH 089/446] Merge description of dotfile volume into the intro
sentence. Content is exactly the same
---
.../en/docs/concepts/configuration/secret.md | 18 ++++++++----------
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/content/en/docs/concepts/configuration/secret.md b/content/en/docs/concepts/configuration/secret.md
index 7ffe4d731d..48e3cc4cb6 100644
--- a/content/en/docs/concepts/configuration/secret.md
+++ b/content/en/docs/concepts/configuration/secret.md
@@ -69,7 +69,14 @@ help automate node registration.
You can make your data "hidden" by defining a key that begins with a dot.
This key represents a dotfile or "hidden" file. For example, when the following secret
-is mounted into a volume, `secret-volume`:
+is mounted into a volume, `secret-volume`, the volume will contain a single file,
+called `.secret-file`, and the `dotfile-test-container` will have this file
+present at the path `/etc/secret-volume/.secret-file`.
+
+{{< note >}}
+Files beginning with dot characters are hidden from the output of `ls -l`;
+you must use `ls -la` to see them when listing directory contents.
+{{< /note >}}
```yaml
apiVersion: v1
@@ -101,15 +108,6 @@ spec:
mountPath: "/etc/secret-volume"
```
-The volume will contain a single file, called `.secret-file`, and
-the `dotfile-test-container` will have this file present at the path
-`/etc/secret-volume/.secret-file`.
-
-{{< note >}}
-Files beginning with dot characters are hidden from the output of `ls -l`;
-you must use `ls -la` to see them when listing directory contents.
-{{< /note >}}
-
### Use case: Secret visible to one container in a Pod
Consider a program that needs to handle HTTP requests, do some complex business
From bb9c7d9d2457070d0d794a50bfeb07422fa86c98 Mon Sep 17 00:00:00 2001
From: Richa Banker
Date: Sun, 23 Jul 2023 15:38:14 -0700
Subject: [PATCH 090/446] Add mvp documentation
Co-authored-by: Tim Bannister
Co-authored-by: Joe Betz
---
.../architecture/mixed-version-proxy.md | 84 +++++++++++++++++++
.../feature-gates.md | 4 +
2 files changed, 88 insertions(+)
create mode 100644 content/en/docs/concepts/architecture/mixed-version-proxy.md
diff --git a/content/en/docs/concepts/architecture/mixed-version-proxy.md b/content/en/docs/concepts/architecture/mixed-version-proxy.md
new file mode 100644
index 0000000000..fd07b140c0
--- /dev/null
+++ b/content/en/docs/concepts/architecture/mixed-version-proxy.md
@@ -0,0 +1,84 @@
+---
+reviewers:
+- jpbetz
+title: Mixed Version Proxy
+content_type: concept
+weight: 220
+---
+
+
+{{< feature-state state="alpha" for_k8s_version="v1.28" >}}
+
+Kubernetes {{< skew currentVersion >}} includes an alpha feature that lets a
+{{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}
+proxy a resource requests to other _peer_ API servers. This is useful when there are multiple
+API servers running different versions of Kubernetes in one cluster (for example, during a long-lived
+rollout to a new release of Kubernetes).
+
+This enables cluster administrators to configure highly available clusters that can be upgraded
+more safely, by directing resource requests (made during the upgrade) to the correct kube-apiserver.
+That proxying prevents users from seeing unexpected 404 Not Found errors that stem
+from the upgrade process.
+
+This mechanism is called the _Mixed Version Proxy_.
+
+## Enabling the Mixed Version Proxy
+Ensure that `UnknownVersionInteroperabilityProxy` [feature gate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/)
+is enabled when you start the {{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}}:
+
+```shell
+kube-apiserver \
+--feature-gates=UnknownVersionInteroperabilityProxy=true \
+# required command line arguments for this feature
+--peer-ca-file=
+--proxy-client-cert-file=,
+--proxy-client-key-file=,
+--requestheader-client-ca-file=,
+# requestheader-allowed-names can be set to blank to allow any Common Name
+--requestheader-allowed-names=,
+
+# optional flags for this feature
+--peer-advertise-ip=`IP of this kube-apiserver that should be used by peers to proxy requests`
+--peer-advertise-port=`port of this kube-apiserver that should be used by peers to proxy requests`
+
+# …and other flags as usual
+```
+
+### Proxy transport and authentication between API servers {#transport-and-authn}
+
+* The source kube-apiserver reuses the [existing APIserver client authentication flags](https://kubernetes.io/docs/tasks/extend-kubernetes/configure-aggregation-layer/#kubernetes-apiserver-client-authentication) `--proxy-client-cert-file` and `--proxy-client-key-file` to present its identity that will be verified by its peer (the destination kube-apiserver). The destination API server verifies that peer connection based on the configuration you specify using the `--requestheader-client-ca-file` command line argument.
+
+* To authenticate the destination server's serving certs, you must configure a certificate authority bundle by specifying the `--peer-ca-file` command line argument to the **source** API server.
+
+### Configuration for peer API server connectivity
+
+To set the network location of a kube-apiserver that peers will use to proxy requests, use the
+`--peer-advertise-ip` and `--peer-advertise-port` command line arguments to kube-apiserver or specify
+these fields in the API server configuration file.
+If these flags are unspecified, peers will use the value from either `--advertise-address` or
+`--bind-address` command line argument to the kube-apiserver. If those too, are unset, the host's default interface is used.
+
+## Mixed version proxying
+
+When you enable mixed version proxying, the [aggregation layer](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/)
+loads a special filter that does the following:
+
+* When a resource request reaches an API server that cannot serve that API (either because it is at a version pre-dating the introduction of the API or the API is turned off on the API server) the API server attempts to send the request to a peer API server that can serve the requested API. It does so by identifying API groups / versions / resources that the local server doesn't recognise, and tries to proxy those requests to a peer API server that is capable of handling the request.
+* If the peer API server fails to respond, the _source_ API server responds with 503("Service Unavailable") error.
+
+### How it works under the hood
+
+When an API Server receives a resource request, it first checks which API servers can serve the requested resource. This check happens using the internal [`StorageVersion` API].
+
+* If the resource is known to the API server that received the request (ex: `GET /api/v1/pods/some-pod`), the request is handled locally.
+
+* If there is no internal `StorageVersion` object found for the requested resource (ex: `GET /my-api/v1/my-resource`) and the configured APIService specifies proxying to an extension API server, that proxying happens following the usual
+[flow](/docs/tasks/extend-kubernetes/configure-aggregation-layer/) for
+extension APIs.
+
+* If a valid internal `StorageVersion` object is found for the requested resource (ex: `GET /batch/v1/jobs`) and the API server trying to handle the request (the _handling API server_) has the `batch` API disabled, then the _handling API server_fetches the peer API servers that do serve the relevant API group / version / resource (`api/v1/batch` in this case) using the information in the fetched `StorageVersion` object. The _handling API server_ then proxies the request to one of the matching peer kube-apiservers that are aware of the requested resource.
+ * If there is no peer known for that API group / version / resource, the handling API server passes the request to its own handler chain which should eventually return a 404("Not Found") response.
+ * If the handling API server has identified and selected a peer API server, but that peer fails
+ to respond (for reasons such as network connectivity issues, or a data race between the request
+ being received and a controller registering the peer's info into the control plane), then the handling
+ API server responds with a 503 (“Service Unavailable”) error.
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 1061a15f5e..cab25fff93 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
@@ -210,6 +210,7 @@ For a reference to old feature gates that are removed, please refer to
| `TopologyManagerPolicyAlphaOptions` | `false` | Alpha | 1.26 | |
| `TopologyManagerPolicyBetaOptions` | `false` | Beta | 1.26 | |
| `TopologyManagerPolicyOptions` | `false` | Alpha | 1.26 | |
+| `UnknownVersionInteroperabilityProxy` | `false` | Alpha | 1.28 | |
| `UserNamespacesStatelessPodsSupport` | `false` | Alpha | 1.25 | |
| `ValidatingAdmissionPolicy` | `false` | Alpha | 1.26 | |
| `VolumeCapacityPriority` | `false` | Alpha | 1.21 | - |
@@ -732,6 +733,9 @@ Each feature gate is designed for enabling/disabling a specific feature:
This feature gate guards *a group* of topology manager options whose quality level is beta.
This feature gate will never graduate to stable.
- `TopologyManagerPolicyOptions`: Allow fine-tuning of topology manager policies,
+- `UnknownVersionInteroperabilityProxy`: Proxy resource requests to the correct peer kube-apiserver when
+ multiple kube-apiservers exist at varied versions.
+ See [Mixed version proxy](/docs/concepts/architecture/mixed-version-proxy/) for more information.
- `UserNamespacesStatelessPodsSupport`: Enable user namespace support for stateless Pods.
- `ValidatingAdmissionPolicy`: Enable [ValidatingAdmissionPolicy](/docs/reference/access-authn-authz/validating-admission-policy/) support for CEL validations be used in Admission Control.
- `VolumeCapacityPriority`: Enable support for prioritizing nodes in different
From fd94278b4e665e87b72af9cae629be4b783ff623 Mon Sep 17 00:00:00 2001
From: andrewsykim
Date: Wed, 26 Jul 2023 12:27:42 -0400
Subject: [PATCH 091/446] update feature gate references for
ProxyTerminatingEndpoint in 1.28
Signed-off-by: andrewsykim
---
.../reference/command-line-tools-reference/feature-gates.md | 5 +++--
content/en/docs/reference/networking/virtual-ips.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 e96f8793ba..d892d3f5be 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
@@ -172,8 +172,6 @@ For a reference to old feature gates that are removed, please refer to
| `ProbeTerminationGracePeriod` | `false` | Beta | 1.22 | 1.24 |
| `ProbeTerminationGracePeriod` | `true` | Beta | 1.25 | |
| `ProcMountType` | `false` | Alpha | 1.12 | |
-| `ProxyTerminatingEndpoints` | `false` | Alpha | 1.22 | 1.25 |
-| `ProxyTerminatingEndpoints` | `true` | Beta | 1.26 | |
| `QOSReserved` | `false` | Alpha | 1.11 | |
| `ReadWriteOncePod` | `false` | Alpha | 1.22 | 1.26 |
| `ReadWriteOncePod` | `true` | Beta | 1.27 | |
@@ -302,6 +300,9 @@ For a reference to old feature gates that are removed, please refer to
| `PodSecurity` | `false` | Alpha | 1.22 | 1.22 |
| `PodSecurity` | `true` | Beta | 1.23 | 1.24 |
| `PodSecurity` | `true` | GA | 1.25 | |
+| `ProxyTerminatingEndpoints` | `false` | Alpha | 1.22 | 1.25 |
+| `ProxyTerminatingEndpoints` | `true` | Beta | 1.26 | 1.27 |
+| `ProxyTerminatingEndpoints` | `true` | GA | 1.28 | - |
| `RemoveSelfLink` | `false` | Alpha | 1.16 | 1.19 |
| `RemoveSelfLink` | `true` | Beta | 1.20 | 1.23 |
| `RemoveSelfLink` | `true` | GA | 1.24 | - |
diff --git a/content/en/docs/reference/networking/virtual-ips.md b/content/en/docs/reference/networking/virtual-ips.md
index c7ac672aad..2c6f0d0209 100644
--- a/content/en/docs/reference/networking/virtual-ips.md
+++ b/content/en/docs/reference/networking/virtual-ips.md
@@ -411,7 +411,7 @@ relevant Service.
### Traffic to terminating endpoints
-{{< feature-state for_k8s_version="v1.26" state="beta" >}}
+{{< feature-state for_k8s_version="v1.28" state="stable" >}}
If the `ProxyTerminatingEndpoints`
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
From 8a3d91e1201d10bbbcbeeb4415de44545b3e2cc6 Mon Sep 17 00:00:00 2001
From: Philippe Martin
Date: Thu, 27 Jul 2023 09:17:23 +0200
Subject: [PATCH 092/446] Update api-ref-generator submodule
---
api-ref-generator | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/api-ref-generator b/api-ref-generator
index 55bce68622..7f83d75831 160000
--- a/api-ref-generator
+++ b/api-ref-generator
@@ -1 +1 @@
-Subproject commit 55bce686224caba37f93e1e1eb53c0c9fc104ed4
+Subproject commit 7f83d75831813de516f88917f138c32d5f712e87
From f301c27b5ed5da36293897e5d301c81b372b91de Mon Sep 17 00:00:00 2001
From: Philippe Martin
Date: Wed, 26 Jul 2023 13:44:50 +0200
Subject: [PATCH 093/446] Update ToC and field description for v1.28
---
api-ref-assets/api/swagger.json | 30048 +++++++---------------------
api-ref-assets/config/fields.yaml | 15 +-
api-ref-assets/config/toc.yaml | 7 +-
3 files changed, 7117 insertions(+), 22953 deletions(-)
diff --git a/api-ref-assets/api/swagger.json b/api-ref-assets/api/swagger.json
index 12903fd69f..d4f1423ba8 100644
--- a/api-ref-assets/api/swagger.json
+++ b/api-ref-assets/api/swagger.json
@@ -37,7 +37,7 @@
"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.",
+ "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 a beta feature and managed by the AdmissionWebhookMatchConditions feature gate.",
"items": {
"$ref": "#/definitions/io.k8s.api.admissionregistration.v1.MatchCondition"
},
@@ -251,7 +251,7 @@
"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.",
+ "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 a beta feature and managed by the AdmissionWebhookMatchConditions feature gate.",
"items": {
"$ref": "#/definitions/io.k8s.api.admissionregistration.v1.MatchCondition"
},
@@ -547,15 +547,23 @@
"x-kubernetes-map-type": "atomic"
},
"io.k8s.api.admissionregistration.v1alpha1.ParamRef": {
- "description": "ParamRef references a parameter resource",
+ "description": "ParamRef describes how to locate the params to be used as input to expressions of rules applied by a policy binding.",
"properties": {
"name": {
- "description": "Name of the resource being referenced.",
+ "description": "`name` is the name of the resource being referenced.\n\n`name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.",
"type": "string"
},
"namespace": {
- "description": "Namespace of the referenced resource. Should be empty for the cluster-scoped resources",
+ "description": "namespace is the namespace of the referenced resource. Allows limiting the search for params to a specific namespace. Applies to both `name` and `selector` fields.\n\nA per-namespace parameter may be used by specifying a namespace-scoped `paramKind` in the policy and leaving this field empty.\n\n- If `paramKind` is cluster-scoped, this field MUST be unset. Setting this field results in a configuration error.\n\n- If `paramKind` is namespace-scoped, the namespace of the object being evaluated for admission will be used when this field is left unset. Take care that if this is left empty the binding must not match any cluster-scoped resources, which will result in an error.",
"type": "string"
+ },
+ "parameterNotFoundAction": {
+ "description": "`parameterNotFoundAction` controls the behavior of the binding when the resource exists, and name or selector is valid, but there are no parameters matched by the binding. If the value is set to `Allow`, then no matched parameters will be treated as successful validation by the binding. If set to `Deny`, then no matched parameters will be subject to the `failurePolicy` of the policy.\n\nAllowed values are `Allow` or `Deny` Default to `Deny`",
+ "type": "string"
+ },
+ "selector": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
+ "description": "selector can be used to match multiple param objects based on their labels. Supply selector: {} to match all resources of the ParamKind.\n\nIf multiple params are found, they are all evaluated with the policy expressions and the results are ANDed together.\n\nOne of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset."
}
},
"type": "object",
@@ -609,7 +617,7 @@
]
},
"io.k8s.api.admissionregistration.v1alpha1.ValidatingAdmissionPolicyBinding": {
- "description": "ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.",
+ "description": "ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.",
"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",
@@ -678,7 +686,7 @@
},
"paramRef": {
"$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.ParamRef",
- "description": "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."
+ "description": "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. If the policy does not specify a ParamKind then this field is ignored, and the rules are evaluated without a param."
},
"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.",
@@ -770,6 +778,19 @@
},
"type": "array",
"x-kubernetes-list-type": "atomic"
+ },
+ "variables": {
+ "description": "Variables contain definitions of variables that can be used in composition of other expressions. Each variable is defined as a named CEL expression. The variables defined here will be available under `variables` in other expressions of the policy except MatchConditions because MatchConditions are evaluated before the rest of the policy.\n\nThe expression of a variable can refer to other variables defined earlier in the list but not those after. Thus, Variables must be sorted by the order of first appearance and acyclic.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1alpha1.Variable"
+ },
+ "type": "array",
+ "x-kubernetes-list-map-keys": [
+ "name"
+ ],
+ "x-kubernetes-list-type": "map",
+ "x-kubernetes-patch-merge-key": "name",
+ "x-kubernetes-patch-strategy": "merge"
}
},
"type": "object"
@@ -804,7 +825,7 @@
"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 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.",
+ "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. - 'namespaceObject' - The namespace object that the incoming object belongs to. The value is null for cluster-scoped resources. - 'variables' - Map of composited variables, from its name to its lazily evaluated value.\n For example, a variable named 'foo' can be accessed as 'variables.foo'.\n- '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": {
@@ -825,6 +846,498 @@
],
"type": "object"
},
+ "io.k8s.api.admissionregistration.v1alpha1.Variable": {
+ "description": "Variable is the definition of a variable that is used for composition.",
+ "properties": {
+ "expression": {
+ "description": "Expression is the expression that will be evaluated as the value of the variable. The CEL expression has access to the same identifiers as the CEL expressions in Validation.",
+ "type": "string"
+ },
+ "name": {
+ "description": "Name is the name of the variable. The name must be a valid CEL identifier and unique among all variables. The variable can be accessed in other expressions through `variables` For example, if name is \"foo\", the variable will be available as `variables.foo`",
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "expression"
+ ],
+ "type": "object"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.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.v1beta1.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.v1beta1.MatchCondition": {
+ "description": "MatchCondition represents a condition which must be 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.v1beta1.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": {
+ "excludeResourceRules": {
+ "description": "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)",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.NamedRuleWithOperations"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "matchPolicy": {
+ "description": "matchPolicy defines how the \"MatchResources\" 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 ValidatingAdmissionPolicy.\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 ValidatingAdmissionPolicy.\n\nDefaults to \"Equivalent\"",
+ "type": "string"
+ },
+ "namespaceSelector": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
+ "description": "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.\n\nFor example, to run the webhook on any objects whose namespace is not associated with \"runlevel\" of \"0\" or \"1\"; you will set the selector as follows: \"namespaceSelector\": {\n \"matchExpressions\": [\n {\n \"key\": \"runlevel\",\n \"operator\": \"NotIn\",\n \"values\": [\n \"0\",\n \"1\"\n ]\n }\n ]\n}\n\nIf instead you want to only run the policy on any objects whose namespace is associated with the \"environment\" of \"prod\" or \"staging\"; you will set the selector as follows: \"namespaceSelector\": {\n \"matchExpressions\": [\n {\n \"key\": \"environment\",\n \"operator\": \"In\",\n \"values\": [\n \"prod\",\n \"staging\"\n ]\n }\n ]\n}\n\nSee https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more examples of label selectors.\n\nDefault to the empty LabelSelector, which matches everything."
+ },
+ "objectSelector": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
+ "description": "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."
+ },
+ "resourceRules": {
+ "description": "ResourceRules describes what operations on what resources/subresources the ValidatingAdmissionPolicy matches. The policy cares about an operation if it matches _any_ Rule.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.NamedRuleWithOperations"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ }
+ },
+ "type": "object",
+ "x-kubernetes-map-type": "atomic"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.NamedRuleWithOperations": {
+ "description": "NamedRuleWithOperations is a tuple of Operations and Resources with ResourceNames.",
+ "properties": {
+ "apiGroups": {
+ "description": "APIGroups is the API groups the resources belong to. '*' is all groups. If '*' is present, the length of the slice must be one. Required.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "apiVersions": {
+ "description": "APIVersions is the API versions the resources belong to. '*' is all versions. If '*' is present, the length of the slice must be one. Required.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "operations": {
+ "description": "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 '*' is present, the length of the slice must be one. Required.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "resourceNames": {
+ "description": "ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "resources": {
+ "description": "Resources is a list of resources this rule applies to.\n\nFor example: 'pods' means pods. 'pods/log' means the log subresource of pods. '*' means all resources, but not subresources. 'pods/*' means all subresources of pods. '*/scale' means all scale subresources. '*/*' means all resources and their subresources.\n\nIf wildcard is present, the validation rule will ensure resources do not overlap with each other.\n\nDepending on the enclosing object, subresources might not be allowed. Required.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "scope": {
+ "description": "scope specifies the scope of this rule. Valid values are \"Cluster\", \"Namespaced\", and \"*\" \"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. Subresources match the scope of their parent resource. Default is \"*\".",
+ "type": "string"
+ }
+ },
+ "type": "object",
+ "x-kubernetes-map-type": "atomic"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ParamKind": {
+ "description": "ParamKind is a tuple of Group Kind and Version.",
+ "properties": {
+ "apiVersion": {
+ "description": "APIVersion is the API group version the resources belong to. In format of \"group/version\". Required.",
+ "type": "string"
+ },
+ "kind": {
+ "description": "Kind is the API kind the resources belong to. Required.",
+ "type": "string"
+ }
+ },
+ "type": "object",
+ "x-kubernetes-map-type": "atomic"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ParamRef": {
+ "description": "ParamRef describes how to locate the params to be used as input to expressions of rules applied by a policy binding.",
+ "properties": {
+ "name": {
+ "description": "name is the name of the resource being referenced.\n\nOne of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.\n\nA single parameter used for all admission requests can be configured by setting the `name` field, leaving `selector` blank, and setting namespace if `paramKind` is namespace-scoped.",
+ "type": "string"
+ },
+ "namespace": {
+ "description": "namespace is the namespace of the referenced resource. Allows limiting the search for params to a specific namespace. Applies to both `name` and `selector` fields.\n\nA per-namespace parameter may be used by specifying a namespace-scoped `paramKind` in the policy and leaving this field empty.\n\n- If `paramKind` is cluster-scoped, this field MUST be unset. Setting this field results in a configuration error.\n\n- If `paramKind` is namespace-scoped, the namespace of the object being evaluated for admission will be used when this field is left unset. Take care that if this is left empty the binding must not match any cluster-scoped resources, which will result in an error.",
+ "type": "string"
+ },
+ "parameterNotFoundAction": {
+ "description": "`parameterNotFoundAction` controls the behavior of the binding when the resource exists, and name or selector is valid, but there are no parameters matched by the binding. If the value is set to `Allow`, then no matched parameters will be treated as successful validation by the binding. If set to `Deny`, then no matched parameters will be subject to the `failurePolicy` of the policy.\n\nAllowed values are `Allow` or `Deny`\n\nRequired",
+ "type": "string"
+ },
+ "selector": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
+ "description": "selector can be used to match multiple param objects based on their labels. Supply selector: {} to match all resources of the ParamKind.\n\nIf multiple params are found, they are all evaluated with the policy expressions and the results are ANDed together.\n\nOne of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset."
+ }
+ },
+ "type": "object",
+ "x-kubernetes-map-type": "atomic"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.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.v1beta1.ExpressionWarning"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ }
+ },
+ "type": "object"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy": {
+ "description": "ValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.",
+ "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 metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata."
+ },
+ "spec": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicySpec",
+ "description": "Specification of the desired behavior of the ValidatingAdmissionPolicy."
+ },
+ "status": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.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",
+ "x-kubernetes-group-version-kind": [
+ {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ ]
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding": {
+ "description": "ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.\n\nFor a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.\n\nThe CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.",
+ "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 metadata; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata."
+ },
+ "spec": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBindingSpec",
+ "description": "Specification of the desired behavior of the ValidatingAdmissionPolicyBinding."
+ }
+ },
+ "type": "object",
+ "x-kubernetes-group-version-kind": [
+ {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ ]
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBindingList": {
+ "description": "ValidatingAdmissionPolicyBindingList is a list of ValidatingAdmissionPolicyBinding.",
+ "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": "List of PolicyBinding.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ },
+ "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 list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds"
+ }
+ },
+ "type": "object",
+ "x-kubernetes-group-version-kind": [
+ {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBindingList",
+ "version": "v1beta1"
+ }
+ ]
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBindingSpec": {
+ "description": "ValidatingAdmissionPolicyBindingSpec is the specification of the ValidatingAdmissionPolicyBinding.",
+ "properties": {
+ "matchResources": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.MatchResources",
+ "description": "MatchResources declares what resources match this binding and will be validated by it. Note that this is intersected with the policy'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."
+ },
+ "paramRef": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ParamRef",
+ "description": "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. If the policy does not specify a ParamKind then this field is ignored, and the rules are evaluated without a param."
+ },
+ "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"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyList": {
+ "description": "ValidatingAdmissionPolicyList is a list of ValidatingAdmissionPolicy.",
+ "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": "List of ValidatingAdmissionPolicy.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ },
+ "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 list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds"
+ }
+ },
+ "type": "object",
+ "x-kubernetes-group-version-kind": [
+ {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyList",
+ "version": "v1beta1"
+ }
+ ]
+ },
+ "io.k8s.api.admissionregistration.v1beta1.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.v1beta1.AuditAnnotation"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "failurePolicy": {
+ "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.v1beta1.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.v1beta1.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."
+ },
+ "paramKind": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ParamKind",
+ "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. Validations and AuditAnnotations may not both be empty; a minimum of one Validations or AuditAnnotations is required.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.Validation"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic"
+ },
+ "variables": {
+ "description": "Variables contain definitions of variables that can be used in composition of other expressions. Each variable is defined as a named CEL expression. The variables defined here will be available under `variables` in other expressions of the policy except MatchConditions because MatchConditions are evaluated before the rest of the policy.\n\nThe expression of a variable can refer to other variables defined earlier in the list but not those after. Thus, Variables must be sorted by the order of first appearance and acyclic.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.Variable"
+ },
+ "type": "array",
+ "x-kubernetes-list-map-keys": [
+ "name"
+ ],
+ "x-kubernetes-list-type": "map",
+ "x-kubernetes-patch-merge-key": "name",
+ "x-kubernetes-patch-strategy": "merge"
+ }
+ },
+ "type": "object"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyStatus": {
+ "description": "ValidatingAdmissionPolicyStatus represents the status of an admission validation policy.",
+ "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.v1beta1.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.v1beta1.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 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. - 'namespaceObject' - The namespace object that the incoming object belongs to. The value is null for cluster-scoped resources. - 'variables' - Map of composited variables, from its name to its lazily evaluated value.\n For example, a variable named 'foo' can be accessed as 'variables.foo'.\n- '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"
+ }
+ },
+ "required": [
+ "expression"
+ ],
+ "type": "object"
+ },
+ "io.k8s.api.admissionregistration.v1beta1.Variable": {
+ "description": "Variable is the definition of a variable that is used for composition. A variable is defined as a named expression.",
+ "properties": {
+ "expression": {
+ "description": "Expression is the expression that will be evaluated as the value of the variable. The CEL expression has access to the same identifiers as the CEL expressions in Validation.",
+ "type": "string"
+ },
+ "name": {
+ "description": "Name is the name of the variable. The name must be a valid CEL identifier and unique among all variables. The variable can be accessed in other expressions through `variables` For example, if name is \"foo\", the variable will be available as `variables.foo`",
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "expression"
+ ],
+ "type": "object",
+ "x-kubernetes-map-type": "atomic"
+ },
"io.k8s.api.apiserverinternal.v1alpha1.ServerStorageVersion": {
"description": "An API server instance reports the version it can decode and the version it encodes objects to when persisting objects in the backend.",
"properties": {
@@ -843,6 +1356,14 @@
"encodingVersion": {
"description": "The API server encodes the object to this version when persisting it in the backend (e.g., etcd).",
"type": "string"
+ },
+ "servedVersions": {
+ "description": "The API server can serve these versions. DecodableVersions must include all ServedVersions.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "set"
}
},
"type": "object"
@@ -1978,6 +2499,45 @@
},
"type": "object"
},
+ "io.k8s.api.authentication.v1.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.v1.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": "v1"
+ }
+ ]
+ },
+ "io.k8s.api.authentication.v1.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.authentication.v1.TokenRequest": {
"description": "TokenRequest requests a token for a given service account.",
"properties": {
@@ -3678,6 +4238,11 @@
"format": "int32",
"type": "integer"
},
+ "backoffLimitPerIndex": {
+ "description": "Specifies the limit for the number of retries within an index before marking this index as failed. When enabled the number of failures per index is kept in the pod's batch.kubernetes.io/job-index-failure-count annotation. It can only be set when Job's completionMode=Indexed, and the Pod's restart policy is Never. The field is immutable. This field is alpha-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).",
+ "format": "int32",
+ "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.",
"type": "string"
@@ -3691,6 +4256,11 @@
"description": "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",
"type": "boolean"
},
+ "maxFailedIndexes": {
+ "description": "Specifies the maximal number of failed indexes before marking the Job as failed, when backoffLimitPerIndex is set. Once the number of failed indexes exceeds this number the entire Job is marked as Failed and its execution is terminated. When left as null the job continues execution of all of its indexes and is marked with the `Complete` Job condition. It can only be specified when backoffLimitPerIndex is set. It can be null or up to completions. It is required and must be less than or equal to 10^4 when is completions greater than 10^5. This field is alpha-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).",
+ "format": "int32",
+ "type": "integer"
+ },
"parallelism": {
"description": "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) < .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/",
"format": "int32",
@@ -3698,7 +4268,11 @@
},
"podFailurePolicy": {
"$ref": "#/definitions/io.k8s.api.batch.v1.PodFailurePolicy",
- "description": "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.\n\nThis field is alpha-level. To use this field, you must enable the `JobPodFailurePolicy` feature gate (disabled by default)."
+ "description": "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.\n\nThis field is beta-level. It can be used when the `JobPodFailurePolicy` feature gate is enabled (enabled by default)."
+ },
+ "podReplacementPolicy": {
+ "description": "podReplacementPolicy specifies when to create replacement Pods. Possible values are: - TerminatingOrFailed means that we recreate pods\n when they are terminating (has a metadata.deletionTimestamp) or failed.\n- Failed means to wait until a previously created Pod is fully terminated (has phase\n Failed or Succeeded) before creating a replacement Pod.\n\nWhen using podFailurePolicy, Failed is the the only allowed value. TerminatingOrFailed and Failed are allowed values when podFailurePolicy is not in use. This is an alpha field. Enable JobPodReplacementPolicy to be able to use this field.",
+ "type": "string"
},
"selector": {
"$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector",
@@ -3754,6 +4328,10 @@
"format": "int32",
"type": "integer"
},
+ "failedIndexes": {
+ "description": "FailedIndexes holds the failed indexes when backoffLimitPerIndex=true. The indexes are represented in the text format analogous as for the `completedIndexes` field, ie. they are kept 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 failed indexes are 1, 3, 4, 5 and 7, they are represented as \"1,3-5,7\". This field is alpha-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).",
+ "type": "string"
+ },
"ready": {
"description": "The number of pods which have a Ready condition.\n\nThis field is beta-level. The job controller populates the field when the feature gate JobReadyPods is enabled (enabled by default).",
"format": "int32",
@@ -3768,6 +4346,11 @@
"format": "int32",
"type": "integer"
},
+ "terminating": {
+ "description": "The number of pods which are terminating (in phase Pending or Running and have a deletionTimestamp).\n\nThis field is alpha-level. The job controller populates the field when the feature gate JobPodReplacementPolicy is enabled (disabled by default).",
+ "format": "int32",
+ "type": "integer"
+ },
"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:\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."
@@ -3855,7 +4438,7 @@
"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:\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.",
+ "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- FailIndex: indicates that the pod's index is marked as Failed and will\n not be restarted.\n This value is alpha-level. It can be used when the\n `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).\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": {
@@ -4671,7 +5254,7 @@
"type": "string"
},
"resourceClaimTemplateName": {
- "description": "ResourceClaimTemplateName is the name of a ResourceClaimTemplate object in the same namespace as this pod.\n\nThe 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 -, where is the PodResourceClaim.Name. Pod validation will reject the pod if the concatenated name is not valid for a ResourceClaim (e.g. too long).\n\nAn 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.\n\nThis field is immutable and no changes will be made to the corresponding ResourceClaim by the control plane after creating the ResourceClaim.",
+ "description": "ResourceClaimTemplateName is the name of a ResourceClaimTemplate object in the same namespace as this pod.\n\nThe 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 pod name and resource name, along with a generated component, will be used to form a unique name for the ResourceClaim, which will be recorded in pod.status.resourceClaimStatuses.\n\nThis field is immutable and no changes will be made to the corresponding ResourceClaim by the control plane after creating the ResourceClaim.",
"type": "string"
}
},
@@ -5059,6 +5642,10 @@
"$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/"
},
+ "restartPolicy": {
+ "description": "RestartPolicy defines the restart behavior of individual containers in a pod. This field may only be set for init containers, and the only allowed value is \"Always\". For non-init containers or when this field is not specified, the restart behavior is defined by the Pod's restart policy and the container type. Setting the RestartPolicy as \"Always\" for the init container will have the following effect: this init container will be continually restarted on exit until all regular containers have terminated. Once all regular containers have completed, all init containers with restartPolicy \"Always\" will be shut down. This lifecycle differs from normal init containers and is often referred to as a \"sidecar\" container. Although this init container still starts in the init container sequence, it does not wait for the container to complete before proceeding to the next init container. Instead, the next init container starts immediately after this init container is started, or after any startupProbe has successfully completed.",
+ "type": "string"
+ },
"securityContext": {
"$ref": "#/definitions/io.k8s.api.core.v1.SecurityContext",
"description": "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/"
@@ -5439,7 +6026,7 @@
"description": "EndpointPort is a tuple that describes a single port.",
"properties": {
"appProtocol": {
- "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.",
+ "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 * 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455\n * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455\n\n* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.",
"type": "string"
},
"name": {
@@ -5700,6 +6287,10 @@
"$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."
},
+ "restartPolicy": {
+ "description": "Restart policy for the container to manage the restart behavior of each container within a pod. This may only be set for init containers. You cannot set this field on ephemeral containers.",
+ "type": "string"
+ },
"securityContext": {
"$ref": "#/definitions/io.k8s.api.core.v1.SecurityContext",
"description": "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."
@@ -6192,7 +6783,7 @@
"description": "HTTPHeader describes a custom header to be used in HTTP probes",
"properties": {
"name": {
- "description": "The header field name",
+ "description": "The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header.",
"type": "string"
},
"value": {
@@ -6223,6 +6814,16 @@
},
"type": "object"
},
+ "io.k8s.api.core.v1.HostIP": {
+ "description": "HostIP represents a single IP address allocated to the host.",
+ "properties": {
+ "ip": {
+ "description": "IP is the IP address assigned to the host",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
"io.k8s.api.core.v1.HostPathVolumeSource": {
"description": "Represents a host path mapped into a pod. Host path volumes do not support ownership management or SELinux relabeling.",
"properties": {
@@ -6552,6 +7153,10 @@
"description": "IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers)",
"type": "string"
},
+ "ipMode": {
+ "description": "IPMode specifies how the load-balancer IP behaves, and may only be specified when the ip field is specified. Setting this to \"VIP\" indicates that traffic is delivered to the node with the destination set to the load-balancer's IP and port. Setting this to \"Proxy\" indicates that traffic is delivered to the node or pod with the destination set to the node's IP and node port or the pod's IP and port. Service implementations may use this information to adjust traffic routing.",
+ "type": "string"
+ },
"ports": {
"description": "Ports is a list of records of service ports If used, every port defined in the service should have an entry in it",
"items": {
@@ -7406,11 +8011,19 @@
},
"type": "array"
},
+ "allocatedResourceStatuses": {
+ "additionalProperties": {
+ "type": "string"
+ },
+ "description": "allocatedResourceStatuses stores status of resource being resized for the given PVC. Key names follow standard Kubernetes label syntax. Valid values are either:\n\t* Un-prefixed keys:\n\t\t- storage - the capacity of the volume.\n\t* Custom resources must use implementation-defined prefixed names such as \"example.com/my-custom-resource\"\nApart from above values - keys that are unprefixed or have kubernetes.io prefix are considered reserved and hence may not be used.\n\nClaimResourceStatus can be in any of following states:\n\t- ControllerResizeInProgress:\n\t\tState set when resize controller starts resizing the volume in control-plane.\n\t- ControllerResizeFailed:\n\t\tState set when resize has failed in resize controller with a terminal error.\n\t- NodeResizePending:\n\t\tState set when resize controller has finished resizing the volume but further resizing of\n\t\tvolume is needed on the node.\n\t- NodeResizeInProgress:\n\t\tState set when kubelet starts resizing the volume.\n\t- NodeResizeFailed:\n\t\tState set when resizing has failed in kubelet with a terminal error. Transient errors don't set\n\t\tNodeResizeFailed.\nFor example: if expanding a PVC for more capacity - this field can be one of the following states:\n\t- pvc.status.allocatedResourceStatus['storage'] = \"ControllerResizeInProgress\"\n - pvc.status.allocatedResourceStatus['storage'] = \"ControllerResizeFailed\"\n - pvc.status.allocatedResourceStatus['storage'] = \"NodeResizePending\"\n - pvc.status.allocatedResourceStatus['storage'] = \"NodeResizeInProgress\"\n - pvc.status.allocatedResourceStatus['storage'] = \"NodeResizeFailed\"\nWhen this field is not set, it means that no resize operation is in progress for the given PVC.\n\nA controller that receives PVC update with previously unknown resourceName or ClaimResourceStatus should ignore the update for the purpose it was designed. For example - a controller that only is responsible for resizing capacity of the volume, should ignore PVC updates that change other valid resources associated with PVC.\n\nThis is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.",
+ "type": "object",
+ "x-kubernetes-map-type": "granular"
+ },
"allocatedResources": {
"additionalProperties": {
"$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
- "description": "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.",
+ "description": "allocatedResources tracks the resources allocated to a PVC including its capacity. Key names follow standard Kubernetes label syntax. Valid values are either:\n\t* Un-prefixed keys:\n\t\t- storage - the capacity of the volume.\n\t* Custom resources must use implementation-defined prefixed names such as \"example.com/my-custom-resource\"\nApart from above values - keys that are unprefixed or have kubernetes.io prefix are considered reserved and hence may not be used.\n\nCapacity reported here 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.\n\nA controller that receives PVC update with previously unknown resourceName should ignore the update for the purpose it was designed. For example - a controller that only is responsible for resizing capacity of the volume, should ignore PVC updates that change other valid resources associated with PVC.\n\nThis is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.",
"type": "object"
},
"capacity": {
@@ -7432,10 +8045,6 @@
"phase": {
"description": "phase represents the current phase of PersistentVolumeClaim.",
"type": "string"
- },
- "resizeStatus": {
- "description": "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.",
- "type": "string"
}
},
"type": "object"
@@ -7648,6 +8257,10 @@
"io.k8s.api.core.v1.PersistentVolumeStatus": {
"description": "PersistentVolumeStatus is the current status of a persistent volume.",
"properties": {
+ "lastPhaseTransitionTime": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time",
+ "description": "lastPhaseTransitionTime is the time the phase transitioned from one to another and automatically resets to current time everytime a volume phase transitions. This is an alpha field and requires enabling PersistentVolumeLastPhaseTransitionTime feature."
+ },
"message": {
"description": "message is a human-readable message indicating details about why the volume is in this state.",
"type": "string"
@@ -7856,10 +8469,10 @@
"type": "object"
},
"io.k8s.api.core.v1.PodIP": {
- "description": "IP address information for entries in the (plural) PodIPs field. Each entry includes:\n\n\tIP: An IP address allocated to the pod. Routable at least within the cluster.",
+ "description": "PodIP represents a single IP address allocated to the pod.",
"properties": {
"ip": {
- "description": "ip is an IP address (IPv4 or IPv6) assigned to the pod",
+ "description": "IP is the IP address assigned to the pod",
"type": "string"
}
},
@@ -7943,6 +8556,23 @@
],
"type": "object"
},
+ "io.k8s.api.core.v1.PodResourceClaimStatus": {
+ "description": "PodResourceClaimStatus is stored in the PodStatus for each PodResourceClaim which references a ResourceClaimTemplate. It stores the generated name for the corresponding ResourceClaim.",
+ "properties": {
+ "name": {
+ "description": "Name uniquely identifies this resource claim inside the pod. This must match the name of an entry in pod.spec.resourceClaims, which implies that the string must be a DNS_LABEL.",
+ "type": "string"
+ },
+ "resourceClaimName": {
+ "description": "ResourceClaimName is the name of the ResourceClaim that was generated for the Pod in the namespace of the Pod. It this is unset, then generating a ResourceClaim was not necessary. The pod.spec.resourceClaims entry can be ignored in this case.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "name"
+ ],
+ "type": "object"
+ },
"io.k8s.api.core.v1.PodSchedulingGate": {
"description": "PodSchedulingGate is associated to a Pod to guard its scheduling.",
"properties": {
@@ -8278,9 +8908,19 @@
"type": "array"
},
"hostIP": {
- "description": "IP address of the host to which the pod is assigned. Empty if not yet scheduled.",
+ "description": "hostIP holds the IP address of the host to which the pod is assigned. Empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns mean that HostIP will not be updated even if there is a node is assigned to pod",
"type": "string"
},
+ "hostIPs": {
+ "description": "hostIPs holds the IP addresses allocated to the host. If this field is specified, the first entry must match the hostIP field. This list is empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns means that HostIPs will not be updated even if there is a node is assigned to this pod.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.core.v1.HostIP"
+ },
+ "type": "array",
+ "x-kubernetes-list-type": "atomic",
+ "x-kubernetes-patch-merge-key": "ip",
+ "x-kubernetes-patch-strategy": "merge"
+ },
"initContainerStatuses": {
"description": "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",
"items": {
@@ -8301,7 +8941,7 @@
"type": "string"
},
"podIP": {
- "description": "IP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.",
+ "description": "podIP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.",
"type": "string"
},
"podIPs": {
@@ -8325,6 +8965,19 @@
"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"
},
+ "resourceClaimStatuses": {
+ "description": "Status of resource claims.",
+ "items": {
+ "$ref": "#/definitions/io.k8s.api.core.v1.PodResourceClaimStatus"
+ },
+ "type": "array",
+ "x-kubernetes-list-map-keys": [
+ "name"
+ ],
+ "x-kubernetes-list-type": "map",
+ "x-kubernetes-patch-merge-key": "name",
+ "x-kubernetes-patch-strategy": "merge,retainKeys"
+ },
"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."
@@ -9180,7 +9833,7 @@
"description": "SeccompProfile defines a pod/container's seccomp profile settings. Only one profile source may be set.",
"properties": {
"localhostProfile": {
- "description": "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's configured seccomp profile location. Must only be set if type is \"Localhost\".",
+ "description": "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's configured seccomp profile location. Must be set if type is \"Localhost\". Must NOT be set for any other type.",
"type": "string"
},
"type": {
@@ -9608,7 +10261,7 @@
"description": "ServicePort contains information on service's 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 * 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455\n * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455\n\n* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.",
"type": "string"
},
"name": {
@@ -9699,7 +10352,7 @@
"type": "string"
},
"loadBalancerIP": {
- "description": "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.",
+ "description": "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. Using it is non-portable and it may not support dual-stack. Users are encouraged to use implementation-specific annotations when available.",
"type": "string"
},
"loadBalancerSourceRanges": {
@@ -10324,7 +10977,7 @@
"type": "string"
},
"hostProcess": {
- "description": "HostProcess determines if a container should be run as a 'Host Process' 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'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.",
+ "description": "HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod'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.",
"type": "boolean"
},
"runAsUserName": {
@@ -10418,7 +11071,7 @@
"description": "EndpointPort represents a Port used by an EndpointSlice",
"properties": {
"appProtocol": {
- "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.",
+ "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 * 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455\n * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455\n\n* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.",
"type": "string"
},
"name": {
@@ -10674,6 +11327,22 @@
],
"type": "object"
},
+ "io.k8s.api.flowcontrol.v1beta2.ExemptPriorityLevelConfiguration": {
+ "description": "ExemptPriorityLevelConfiguration describes the configurable aspects of the handling of exempt requests. In the mandatory exempt configuration object the values in the fields here can be modified by authorized users, unlike the rest of the `spec`.",
+ "properties": {
+ "lendablePercent": {
+ "description": "`lendablePercent` prescribes the fraction of the level's NominalCL that can be borrowed by other priority levels. This 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's LendableConcurrencyLimit (LendableCL), is defined as follows.\n\nLendableCL(i) = round( NominalCL(i) * lendablePercent(i)/100.0 )",
+ "format": "int32",
+ "type": "integer"
+ },
+ "nominalConcurrencyShares": {
+ "description": "`nominalConcurrencyShares` (NCS) contributes to the computation of the NominalConcurrencyLimit (NominalCL) of this level. This is the number of execution seats nominally reserved for this priority level. This DOES NOT limit the dispatching from this priority level but affects the other priority levels through the borrowing mechanism. The server's concurrency limit (ServerCL) is divided among all the priority levels in proportion to their NCS values:\n\nNominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[priority level k] NCS(k)\n\nBigger numbers mean a larger nominal concurrency limit, at the expense of every other priority level. This field has a default value of zero.",
+ "format": "int32",
+ "type": "integer"
+ }
+ },
+ "type": "object"
+ },
"io.k8s.api.flowcontrol.v1beta2.FlowDistinguisherMethod": {
"description": "FlowDistinguisherMethod specifies the method of a flow distinguisher.",
"properties": {
@@ -11060,6 +11729,10 @@
"io.k8s.api.flowcontrol.v1beta2.PriorityLevelConfigurationSpec": {
"description": "PriorityLevelConfigurationSpec specifies the configuration of a priority level.",
"properties": {
+ "exempt": {
+ "$ref": "#/definitions/io.k8s.api.flowcontrol.v1beta2.ExemptPriorityLevelConfiguration",
+ "description": "`exempt` specifies how requests are handled for an exempt priority level. This field MUST be empty if `type` is `\"Limited\"`. This field MAY be non-empty if `type` is `\"Exempt\"`. If empty and `type` is `\"Exempt\"` then the default values for `ExemptPriorityLevelConfiguration` apply."
+ },
"limited": {
"$ref": "#/definitions/io.k8s.api.flowcontrol.v1beta2.LimitedPriorityLevelConfiguration",
"description": "`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `\"Limited\"`."
@@ -11077,6 +11750,7 @@
{
"discriminator": "type",
"fields-to-discriminateBy": {
+ "exempt": "Exempt",
"limited": "Limited"
}
}
@@ -11233,6 +11907,22 @@
],
"type": "object"
},
+ "io.k8s.api.flowcontrol.v1beta3.ExemptPriorityLevelConfiguration": {
+ "description": "ExemptPriorityLevelConfiguration describes the configurable aspects of the handling of exempt requests. In the mandatory exempt configuration object the values in the fields here can be modified by authorized users, unlike the rest of the `spec`.",
+ "properties": {
+ "lendablePercent": {
+ "description": "`lendablePercent` prescribes the fraction of the level's NominalCL that can be borrowed by other priority levels. This 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's LendableConcurrencyLimit (LendableCL), is defined as follows.\n\nLendableCL(i) = round( NominalCL(i) * lendablePercent(i)/100.0 )",
+ "format": "int32",
+ "type": "integer"
+ },
+ "nominalConcurrencyShares": {
+ "description": "`nominalConcurrencyShares` (NCS) contributes to the computation of the NominalConcurrencyLimit (NominalCL) of this level. This is the number of execution seats nominally reserved for this priority level. This DOES NOT limit the dispatching from this priority level but affects the other priority levels through the borrowing mechanism. The server's concurrency limit (ServerCL) is divided among all the priority levels in proportion to their NCS values:\n\nNominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[priority level k] NCS(k)\n\nBigger numbers mean a larger nominal concurrency limit, at the expense of every other priority level. This field has a default value of zero.",
+ "format": "int32",
+ "type": "integer"
+ }
+ },
+ "type": "object"
+ },
"io.k8s.api.flowcontrol.v1beta3.FlowDistinguisherMethod": {
"description": "FlowDistinguisherMethod specifies the method of a flow distinguisher.",
"properties": {
@@ -11445,7 +12135,7 @@
"description": "`limitResponse` indicates what to do with requests that can not be executed right now"
},
"nominalConcurrencyShares": {
- "description": "`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's concurrency limit (ServerCL) is divided among the Limited priority levels in proportion to their NCS values:\n\nNominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[limited priority level k] NCS(k)\n\nBigger numbers mean a larger nominal concurrency limit, at the expense of every other Limited priority level. This field has a default value of 30.",
+ "description": "`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's concurrency limit (ServerCL) is divided among the Limited priority levels in proportion to their NCS values:\n\nNominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[priority level k] NCS(k)\n\nBigger numbers mean a larger nominal concurrency limit, at the expense of every other priority level. This field has a default value of 30.",
"format": "int32",
"type": "integer"
}
@@ -11621,6 +12311,10 @@
"io.k8s.api.flowcontrol.v1beta3.PriorityLevelConfigurationSpec": {
"description": "PriorityLevelConfigurationSpec specifies the configuration of a priority level.",
"properties": {
+ "exempt": {
+ "$ref": "#/definitions/io.k8s.api.flowcontrol.v1beta3.ExemptPriorityLevelConfiguration",
+ "description": "`exempt` specifies how requests are handled for an exempt priority level. This field MUST be empty if `type` is `\"Limited\"`. This field MAY be non-empty if `type` is `\"Exempt\"`. If empty and `type` is `\"Exempt\"` then the default values for `ExemptPriorityLevelConfiguration` apply."
+ },
"limited": {
"$ref": "#/definitions/io.k8s.api.flowcontrol.v1beta3.LimitedPriorityLevelConfiguration",
"description": "`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `\"Limited\"`."
@@ -11638,6 +12332,7 @@
{
"discriminator": "type",
"fields-to-discriminateBy": {
+ "exempt": "Exempt",
"limited": "Limited"
}
}
@@ -12209,10 +12904,6 @@
"spec": {
"$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicySpec",
"description": "spec represents the specification of the desired behavior for this NetworkPolicy."
- },
- "status": {
- "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicyStatus",
- "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",
@@ -12370,25 +13061,6 @@
],
"type": "object"
},
- "io.k8s.api.networking.v1.NetworkPolicyStatus": {
- "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",
- "items": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Condition"
- },
- "type": "array",
- "x-kubernetes-list-map-keys": [
- "type"
- ],
- "x-kubernetes-list-type": "map",
- "x-kubernetes-patch-merge-key": "type",
- "x-kubernetes-patch-strategy": "merge"
- }
- },
- "type": "object"
- },
"io.k8s.api.networking.v1.ServiceBackendPort": {
"description": "ServiceBackendPort is the service port being referenced.",
"properties": {
@@ -12947,7 +13619,7 @@
},
"roleRef": {
"$ref": "#/definitions/io.k8s.api.rbac.v1.RoleRef",
- "description": "RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error."
+ "description": "RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error. This field is immutable."
},
"subjects": {
"description": "Subjects holds references to the objects the role applies to.",
@@ -13132,7 +13804,7 @@
},
"roleRef": {
"$ref": "#/definitions/io.k8s.api.rbac.v1.RoleRef",
- "description": "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."
+ "description": "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. This field is immutable."
},
"subjects": {
"description": "Subjects holds references to the objects the role applies to.",
@@ -15066,6 +15738,10 @@
"io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1.ValidationRule": {
"description": "ValidationRule describes a validation rule written in the CEL expression language.",
"properties": {
+ "fieldPath": {
+ "description": "fieldPath represents the field path returned when the validation fails. It must be a relative JSON path (i.e. with array notation) scoped to the location of this x-kubernetes-validations extension in the schema and refer to an existing field. e.g. when validation checks if a specific attribute `foo` under a map `testMap`, the fieldPath could be set to `.testMap.foo` If the validation checks two lists must have unique attributes, the fieldPath could be set to either of the list: e.g. `.testList` It does not support list numeric index. It supports child operation to refer to an existing field currently. Refer to [JSONPath support in Kubernetes](https://kubernetes.io/docs/reference/kubectl/jsonpath/) for more info. Numeric index of array is not supported. For field name which contains special characters, use `['specialName']` to refer the field name. e.g. for attribute `foo.34$` appears in a list `testList`, the fieldPath could be set to `.testList['foo.34$']`",
+ "type": "string"
+ },
"message": {
"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"
@@ -15074,6 +15750,10 @@
"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"
},
+ "reason": {
+ "description": "reason provides a machine-readable validation failure reason that is returned to the caller when a request fails this validation rule. The HTTP status code returned to the caller will match the reason of the reason of the first failed validation rule. The currently supported reasons are: \"FieldValueInvalid\", \"FieldValueForbidden\", \"FieldValueRequired\", \"FieldValueDuplicate\". If not set, default to use \"FieldValueInvalid\". All future added reasons must be accepted by clients when reading this value and unknown reasons should be treated as FieldValueInvalid.",
+ "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"
@@ -15758,9 +16438,7 @@
"properties": {
"key": {
"description": "key is the label key that the selector applies to.",
- "type": "string",
- "x-kubernetes-patch-merge-key": "key",
- "x-kubernetes-patch-strategy": "merge"
+ "type": "string"
},
"operator": {
"description": "operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.",
@@ -16654,6 +17332,327 @@
"title": "Kubernetes",
"version": "unversioned"
},
+ "parameters": {
+ "allowWatchBookmarks-HC2hJt-J": {
+ "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
+ },
+ "body-2Y1dVQaQ": {
+ "in": "body",
+ "name": "body",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
+ }
+ },
+ "body-78PwaGsr": {
+ "in": "body",
+ "name": "body",
+ "required": true,
+ "schema": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
+ }
+ },
+ "command-Py3eQybp": {
+ "description": "Command is the remote command to execute. argv array. Not executed within a shell.",
+ "in": "query",
+ "name": "command",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "container-1GeXxFDC": {
+ "description": "The container for which to stream logs. Defaults to only container if there is one container in the pod.",
+ "in": "query",
+ "name": "container",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "container-_Q-EJ3nR": {
+ "description": "The container in which to execute the command. Defaults to only container if there is only one container in the pod.",
+ "in": "query",
+ "name": "container",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "container-i5dOmRiM": {
+ "description": "Container in which to execute the command. Defaults to only container if there is only one container in the pod.",
+ "in": "query",
+ "name": "container",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "continue-QfD61s0i": {
+ "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
+ },
+ "fieldManager-7c6nTn1T": {
+ "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
+ },
+ "fieldManager-Qy4HdaTW": {
+ "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
+ },
+ "fieldSelector-xIcQKXFG": {
+ "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
+ "in": "query",
+ "name": "fieldSelector",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "follow-9OIXh_2R": {
+ "description": "Follow the log stream of the pod. Defaults to false.",
+ "in": "query",
+ "name": "follow",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "force-tOGGb0Yi": {
+ "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
+ },
+ "gracePeriodSeconds--K5HaBOS": {
+ "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
+ },
+ "insecureSkipTLSVerifyBackend-gM00jVbe": {
+ "description": "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).",
+ "in": "query",
+ "name": "insecureSkipTLSVerifyBackend",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "labelSelector-5Zw57w4C": {
+ "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
+ "in": "query",
+ "name": "labelSelector",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "limit-1NfNmdNH": {
+ "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
+ },
+ "limitBytes-zwd1RXuc": {
+ "description": "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.",
+ "in": "query",
+ "name": "limitBytes",
+ "type": "integer",
+ "uniqueItems": true
+ },
+ "logpath-Noq7euwC": {
+ "description": "path to the log",
+ "in": "path",
+ "name": "logpath",
+ "required": true,
+ "type": "string",
+ "uniqueItems": true
+ },
+ "namespace-vgWSWtn3": {
+ "description": "object name and auth scope, such as for teams and projects",
+ "in": "path",
+ "name": "namespace",
+ "required": true,
+ "type": "string",
+ "uniqueItems": true
+ },
+ "orphanDependents-uRB25kX5": {
+ "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
+ },
+ "path-QCf0eosM": {
+ "description": "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.",
+ "in": "query",
+ "name": "path",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "path-oPbzgLUj": {
+ "description": "Path is the URL path to use for the current proxy request to pod.",
+ "in": "query",
+ "name": "path",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "path-rFDtV0x9": {
+ "description": "Path is the URL path to use for the current proxy request to node.",
+ "in": "query",
+ "name": "path",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "path-z6Ciiujn": {
+ "description": "path to the resource",
+ "in": "path",
+ "name": "path",
+ "required": true,
+ "type": "string",
+ "uniqueItems": true
+ },
+ "ports-91KROJmm": {
+ "description": "List of ports to forward Required when using WebSockets",
+ "in": "query",
+ "name": "ports",
+ "type": "integer",
+ "uniqueItems": true
+ },
+ "pretty-nN7o5FEq": {
+ "description": "If 'true', then the output is pretty printed.",
+ "in": "query",
+ "name": "pretty",
+ "type": "string",
+ "uniqueItems": true
+ },
+ "previous-1jxDPu3y": {
+ "description": "Return previous terminated container logs. Defaults to false.",
+ "in": "query",
+ "name": "previous",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "propagationPolicy-6jk3prlO": {
+ "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
+ },
+ "resourceVersion-5WAnf1kx": {
+ "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
+ },
+ "resourceVersionMatch-t8XhRHeC": {
+ "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
+ },
+ "sendInitialEvents-rLXlEK_k": {
+ "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
+ "in": "query",
+ "name": "sendInitialEvents",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "sinceSeconds-vE2NLdnP": {
+ "description": "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.",
+ "in": "query",
+ "name": "sinceSeconds",
+ "type": "integer",
+ "uniqueItems": true
+ },
+ "stderr-26jJhFUR": {
+ "description": "Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true.",
+ "in": "query",
+ "name": "stderr",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "stderr-W_1TNlWc": {
+ "description": "Redirect the standard error stream of the pod for this call.",
+ "in": "query",
+ "name": "stderr",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "stdin-PSzNhyUC": {
+ "description": "Redirect the standard input stream of the pod for this call. Defaults to false.",
+ "in": "query",
+ "name": "stdin",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "stdin-sEFnN3IS": {
+ "description": "Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false.",
+ "in": "query",
+ "name": "stdin",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "stdout--EZLRwV1": {
+ "description": "Redirect the standard output stream of the pod for this call.",
+ "in": "query",
+ "name": "stdout",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "stdout-005YMKE6": {
+ "description": "Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true.",
+ "in": "query",
+ "name": "stdout",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "tailLines-2fRTNzbP": {
+ "description": "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",
+ "in": "query",
+ "name": "tailLines",
+ "type": "integer",
+ "uniqueItems": true
+ },
+ "timeoutSeconds-yvYezaOC": {
+ "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
+ },
+ "timestamps-c17fW1w_": {
+ "description": "If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false.",
+ "in": "query",
+ "name": "timestamps",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "tty-g7MlET_l": {
+ "description": "TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. Defaults to false.",
+ "in": "query",
+ "name": "tty",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "tty-s0flW37O": {
+ "description": "TTY if true indicates that a tty will be allocated for the exec call. Defaults to false.",
+ "in": "query",
+ "name": "tty",
+ "type": "boolean",
+ "uniqueItems": true
+ },
+ "watch-XNNPZGbK": {
+ "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
+ }
+ },
"paths": {
"/.well-known/openid-configuration/": {
"get": {
@@ -16787,81 +17786,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -16911,11 +17866,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
]
},
@@ -16959,81 +17910,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -17077,81 +17984,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -17195,81 +18058,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -17313,81 +18132,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -17400,74 +18175,34 @@
"operationId": "listCoreV1Namespace",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -17503,11 +18238,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -17533,11 +18264,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -17599,11 +18326,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -17613,19 +18336,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -17695,18 +18409,10 @@
"operationId": "deleteCoreV1CollectionNamespacedConfigMap",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -17716,74 +18422,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -17823,74 +18489,34 @@
"operationId": "listCoreV1NamespacedConfigMap",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -17926,19 +18552,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -17964,11 +18581,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -18029,11 +18642,7 @@
"operationId": "deleteCoreV1NamespacedConfigMap",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -18043,25 +18652,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -18144,19 +18741,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -18170,12 +18758,7 @@
"operationId": "patchCoreV1NamespacedConfigMap",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -18185,11 +18768,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -18199,11 +18778,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -18264,11 +18839,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -18323,18 +18894,10 @@
"operationId": "deleteCoreV1CollectionNamespacedEndpoints",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -18344,74 +18907,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -18451,74 +18974,34 @@
"operationId": "listCoreV1NamespacedEndpoints",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -18554,19 +19037,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -18592,11 +19066,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -18657,11 +19127,7 @@
"operationId": "deleteCoreV1NamespacedEndpoints",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -18671,25 +19137,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -18772,19 +19226,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -18798,12 +19243,7 @@
"operationId": "patchCoreV1NamespacedEndpoints",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -18813,11 +19253,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -18827,11 +19263,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -18892,11 +19324,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -18951,18 +19379,10 @@
"operationId": "deleteCoreV1CollectionNamespacedEvent",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -18972,74 +19392,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -19079,74 +19459,34 @@
"operationId": "listCoreV1NamespacedEvent",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -19182,19 +19522,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -19220,11 +19551,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -19285,11 +19612,7 @@
"operationId": "deleteCoreV1NamespacedEvent",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -19299,25 +19622,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -19400,19 +19711,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -19426,12 +19728,7 @@
"operationId": "patchCoreV1NamespacedEvent",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -19441,11 +19738,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -19455,11 +19748,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -19520,11 +19809,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -19579,18 +19864,10 @@
"operationId": "deleteCoreV1CollectionNamespacedLimitRange",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -19600,74 +19877,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -19707,74 +19944,34 @@
"operationId": "listCoreV1NamespacedLimitRange",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -19810,19 +20007,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -19848,11 +20036,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -19913,11 +20097,7 @@
"operationId": "deleteCoreV1NamespacedLimitRange",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -19927,25 +20107,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -20028,19 +20196,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -20054,12 +20213,7 @@
"operationId": "patchCoreV1NamespacedLimitRange",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -20069,11 +20223,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -20083,11 +20233,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -20148,11 +20294,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -20207,18 +20349,10 @@
"operationId": "deleteCoreV1CollectionNamespacedPersistentVolumeClaim",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -20228,74 +20362,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -20335,74 +20429,34 @@
"operationId": "listCoreV1NamespacedPersistentVolumeClaim",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -20438,19 +20492,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -20476,11 +20521,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -20541,11 +20582,7 @@
"operationId": "deleteCoreV1NamespacedPersistentVolumeClaim",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -20555,25 +20592,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -20656,19 +20681,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -20682,12 +20698,7 @@
"operationId": "patchCoreV1NamespacedPersistentVolumeClaim",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -20697,11 +20708,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -20711,11 +20718,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -20776,11 +20779,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -20872,19 +20871,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -20898,12 +20888,7 @@
"operationId": "patchCoreV1NamespacedPersistentVolumeClaimStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -20913,11 +20898,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -20927,11 +20908,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -20992,11 +20969,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -21051,18 +21024,10 @@
"operationId": "deleteCoreV1CollectionNamespacedPod",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -21072,74 +21037,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -21179,74 +21104,34 @@
"operationId": "listCoreV1NamespacedPod",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -21282,19 +21167,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -21320,11 +21196,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -21385,11 +21257,7 @@
"operationId": "deleteCoreV1NamespacedPod",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -21399,25 +21267,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -21500,19 +21356,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -21526,12 +21373,7 @@
"operationId": "patchCoreV1NamespacedPod",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -21541,11 +21383,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -21555,11 +21393,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -21620,11 +21454,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -21706,11 +21536,7 @@
},
"parameters": [
{
- "description": "The container in which to execute the command. Defaults to only container if there is only one container in the pod.",
- "in": "query",
- "name": "container",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/container-_Q-EJ3nR"
},
{
"description": "name of the PodAttachOptions",
@@ -21721,40 +21547,19 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true.",
- "in": "query",
- "name": "stderr",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/stderr-26jJhFUR"
},
{
- "description": "Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false.",
- "in": "query",
- "name": "stdin",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/stdin-sEFnN3IS"
},
{
- "description": "Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true.",
- "in": "query",
- "name": "stdout",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/stdout-005YMKE6"
},
{
- "description": "TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. Defaults to false.",
- "in": "query",
- "name": "tty",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/tty-g7MlET_l"
}
],
"post": {
@@ -21801,11 +21606,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -21823,19 +21624,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -21942,19 +21734,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -21968,12 +21751,7 @@
"operationId": "patchCoreV1NamespacedPodEphemeralcontainers",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -21983,11 +21761,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -21997,11 +21771,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -22062,11 +21832,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -22122,11 +21888,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -22144,19 +21906,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -22253,18 +22006,10 @@
},
"parameters": [
{
- "description": "Command is the remote command to execute. argv array. Not executed within a shell.",
- "in": "query",
- "name": "command",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/command-Py3eQybp"
},
{
- "description": "Container in which to execute the command. Defaults to only container if there is only one container in the pod.",
- "in": "query",
- "name": "container",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/container-i5dOmRiM"
},
{
"description": "name of the PodExecOptions",
@@ -22275,40 +22020,19 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "Redirect the standard error stream of the pod for this call.",
- "in": "query",
- "name": "stderr",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/stderr-W_1TNlWc"
},
{
- "description": "Redirect the standard input stream of the pod for this call. Defaults to false.",
- "in": "query",
- "name": "stdin",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/stdin-PSzNhyUC"
},
{
- "description": "Redirect the standard output stream of the pod for this call.",
- "in": "query",
- "name": "stdout",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/stdout--EZLRwV1"
},
{
- "description": "TTY if true indicates that a tty will be allocated for the exec call. Defaults to false.",
- "in": "query",
- "name": "tty",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/tty-s0flW37O"
}
],
"post": {
@@ -22384,32 +22108,16 @@
},
"parameters": [
{
- "description": "The container for which to stream logs. Defaults to only container if there is one container in the pod.",
- "in": "query",
- "name": "container",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/container-1GeXxFDC"
},
{
- "description": "Follow the log stream of the pod. Defaults to false.",
- "in": "query",
- "name": "follow",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/follow-9OIXh_2R"
},
{
- "description": "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).",
- "in": "query",
- "name": "insecureSkipTLSVerifyBackend",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/insecureSkipTLSVerifyBackend-gM00jVbe"
},
{
- "description": "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.",
- "in": "query",
- "name": "limitBytes",
- "type": "integer",
- "uniqueItems": true
+ "$ref": "#/parameters/limitBytes-zwd1RXuc"
},
{
"description": "name of the Pod",
@@ -22420,47 +22128,22 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "description": "Return previous terminated container logs. Defaults to false.",
- "in": "query",
- "name": "previous",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/previous-1jxDPu3y"
},
{
- "description": "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.",
- "in": "query",
- "name": "sinceSeconds",
- "type": "integer",
- "uniqueItems": true
+ "$ref": "#/parameters/sinceSeconds-vE2NLdnP"
},
{
- "description": "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",
- "in": "query",
- "name": "tailLines",
- "type": "integer",
- "uniqueItems": true
+ "$ref": "#/parameters/tailLines-2fRTNzbP"
},
{
- "description": "If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false.",
- "in": "query",
- "name": "timestamps",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/timestamps-c17fW1w_"
}
]
},
@@ -22508,19 +22191,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "List of ports to forward Required when using WebSockets",
- "in": "query",
- "name": "ports",
- "type": "integer",
- "uniqueItems": true
+ "$ref": "#/parameters/ports-91KROJmm"
}
],
"post": {
@@ -22700,19 +22374,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "Path is the URL path to use for the current proxy request to pod.",
- "in": "query",
- "name": "path",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-oPbzgLUj"
}
],
"patch": {
@@ -22958,27 +22623,13 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "path to the resource",
- "in": "path",
- "name": "path",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-z6Ciiujn"
},
{
- "description": "Path is the URL path to use for the current proxy request to pod.",
- "in": "query",
- "name": "path",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-oPbzgLUj"
}
],
"patch": {
@@ -23127,19 +22778,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -23153,12 +22795,7 @@
"operationId": "patchCoreV1NamespacedPodStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -23168,11 +22805,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -23182,11 +22815,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -23247,11 +22876,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -23306,18 +22931,10 @@
"operationId": "deleteCoreV1CollectionNamespacedPodTemplate",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -23327,74 +22944,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -23434,74 +23011,34 @@
"operationId": "listCoreV1NamespacedPodTemplate",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -23537,19 +23074,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -23575,11 +23103,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -23640,11 +23164,7 @@
"operationId": "deleteCoreV1NamespacedPodTemplate",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -23654,25 +23174,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -23755,19 +23263,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -23781,12 +23280,7 @@
"operationId": "patchCoreV1NamespacedPodTemplate",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -23796,11 +23290,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -23810,11 +23300,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -23875,11 +23361,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -23934,18 +23416,10 @@
"operationId": "deleteCoreV1CollectionNamespacedReplicationController",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -23955,74 +23429,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -24062,74 +23496,34 @@
"operationId": "listCoreV1NamespacedReplicationController",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -24165,19 +23559,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -24203,11 +23588,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -24268,11 +23649,7 @@
"operationId": "deleteCoreV1NamespacedReplicationController",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -24282,25 +23659,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -24383,19 +23748,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -24409,12 +23765,7 @@
"operationId": "patchCoreV1NamespacedReplicationController",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -24424,11 +23775,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -24438,11 +23785,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -24503,11 +23846,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -24599,19 +23938,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -24625,12 +23955,7 @@
"operationId": "patchCoreV1NamespacedReplicationControllerScale",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -24640,11 +23965,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -24654,11 +23975,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -24719,11 +24036,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -24815,19 +24128,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -24841,12 +24145,7 @@
"operationId": "patchCoreV1NamespacedReplicationControllerStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -24856,11 +24155,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -24870,11 +24165,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -24935,11 +24226,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -24994,18 +24281,10 @@
"operationId": "deleteCoreV1CollectionNamespacedResourceQuota",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -25015,74 +24294,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -25122,74 +24361,34 @@
"operationId": "listCoreV1NamespacedResourceQuota",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -25225,19 +24424,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -25263,11 +24453,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -25328,11 +24514,7 @@
"operationId": "deleteCoreV1NamespacedResourceQuota",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -25342,25 +24524,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -25443,19 +24613,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -25469,12 +24630,7 @@
"operationId": "patchCoreV1NamespacedResourceQuota",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -25484,11 +24640,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -25498,11 +24650,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -25563,11 +24711,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -25659,19 +24803,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -25685,12 +24820,7 @@
"operationId": "patchCoreV1NamespacedResourceQuotaStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -25700,11 +24830,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -25714,11 +24840,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -25779,11 +24901,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -25838,18 +24956,10 @@
"operationId": "deleteCoreV1CollectionNamespacedSecret",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -25859,74 +24969,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -25966,74 +25036,34 @@
"operationId": "listCoreV1NamespacedSecret",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -26069,19 +25099,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -26107,11 +25128,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -26172,11 +25189,7 @@
"operationId": "deleteCoreV1NamespacedSecret",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -26186,25 +25199,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -26287,19 +25288,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -26313,12 +25305,7 @@
"operationId": "patchCoreV1NamespacedSecret",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -26328,11 +25315,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -26342,11 +25325,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -26407,11 +25386,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -26466,18 +25441,10 @@
"operationId": "deleteCoreV1CollectionNamespacedServiceAccount",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -26487,74 +25454,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -26594,74 +25521,34 @@
"operationId": "listCoreV1NamespacedServiceAccount",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -26697,19 +25584,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -26735,11 +25613,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -26800,11 +25674,7 @@
"operationId": "deleteCoreV1NamespacedServiceAccount",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -26814,25 +25684,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -26915,19 +25773,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -26941,12 +25790,7 @@
"operationId": "patchCoreV1NamespacedServiceAccount",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -26956,11 +25800,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -26970,11 +25810,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -27035,11 +25871,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -27095,11 +25927,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -27117,19 +25945,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -27199,18 +26018,10 @@
"operationId": "deleteCoreV1CollectionNamespacedService",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -27220,74 +26031,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -27327,74 +26098,34 @@
"operationId": "listCoreV1NamespacedService",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -27430,19 +26161,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -27468,11 +26190,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -27533,11 +26251,7 @@
"operationId": "deleteCoreV1NamespacedService",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -27547,25 +26261,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -27648,19 +26350,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -27674,12 +26367,7 @@
"operationId": "patchCoreV1NamespacedService",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -27689,11 +26377,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -27703,11 +26387,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -27768,11 +26448,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -27961,19 +26637,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "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.",
- "in": "query",
- "name": "path",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-QCf0eosM"
}
],
"patch": {
@@ -28219,27 +26886,13 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "path to the resource",
- "in": "path",
- "name": "path",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-z6Ciiujn"
},
{
- "description": "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.",
- "in": "query",
- "name": "path",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-QCf0eosM"
}
],
"patch": {
@@ -28388,19 +27041,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -28414,12 +27058,7 @@
"operationId": "patchCoreV1NamespacedServiceStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -28429,11 +27068,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -28443,11 +27078,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -28508,11 +27139,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -28567,11 +27194,7 @@
"operationId": "deleteCoreV1Namespace",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -28581,25 +27204,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -28682,11 +27293,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -28700,12 +27307,7 @@
"operationId": "patchCoreV1Namespace",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -28715,11 +27317,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -28729,11 +27327,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -28794,11 +27388,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -28854,11 +27444,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -28876,11 +27462,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"put": {
@@ -28981,11 +27563,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -28999,12 +27577,7 @@
"operationId": "patchCoreV1NamespaceStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -29014,11 +27587,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -29028,11 +27597,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -29093,11 +27658,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -29152,18 +27713,10 @@
"operationId": "deleteCoreV1CollectionNode",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -29173,74 +27726,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -29280,74 +27793,34 @@
"operationId": "listCoreV1Node",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -29383,11 +27856,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -29413,11 +27882,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -29478,11 +27943,7 @@
"operationId": "deleteCoreV1Node",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -29492,25 +27953,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -29593,11 +28042,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -29611,12 +28056,7 @@
"operationId": "patchCoreV1Node",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -29626,11 +28066,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -29640,11 +28076,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -29705,11 +28137,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -29898,11 +28326,7 @@
"uniqueItems": true
},
{
- "description": "Path is the URL path to use for the current proxy request to node.",
- "in": "query",
- "name": "path",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-rFDtV0x9"
}
],
"patch": {
@@ -30148,19 +28572,10 @@
"uniqueItems": true
},
{
- "description": "path to the resource",
- "in": "path",
- "name": "path",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-z6Ciiujn"
},
{
- "description": "Path is the URL path to use for the current proxy request to node.",
- "in": "query",
- "name": "path",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/path-rFDtV0x9"
}
],
"patch": {
@@ -30309,11 +28724,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -30327,12 +28738,7 @@
"operationId": "patchCoreV1NodeStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -30342,11 +28748,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -30356,11 +28758,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -30421,11 +28819,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -30511,81 +28905,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -30598,18 +28948,10 @@
"operationId": "deleteCoreV1CollectionPersistentVolume",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -30619,74 +28961,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -30726,74 +29028,34 @@
"operationId": "listCoreV1PersistentVolume",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -30829,11 +29091,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -30859,11 +29117,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -30924,11 +29178,7 @@
"operationId": "deleteCoreV1PersistentVolume",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -30938,25 +29188,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -31039,11 +29277,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -31057,12 +29291,7 @@
"operationId": "patchCoreV1PersistentVolume",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -31072,11 +29301,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -31086,11 +29311,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -31151,11 +29372,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -31247,11 +29464,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -31265,12 +29478,7 @@
"operationId": "patchCoreV1PersistentVolumeStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -31280,11 +29488,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -31294,11 +29498,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -31359,11 +29559,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -31449,81 +29645,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -31567,81 +29719,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -31685,81 +29793,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -31803,81 +29867,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -31921,81 +29941,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32039,81 +30015,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32157,81 +30089,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32275,81 +30163,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32393,81 +30237,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32511,81 +30311,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32629,81 +30385,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32747,81 +30459,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32865,89 +30533,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -32991,39 +30610,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ConfigMap",
@@ -33034,54 +30633,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -33125,89 +30695,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -33251,39 +30772,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Endpoints",
@@ -33294,54 +30795,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -33385,89 +30857,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -33511,39 +30934,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Event",
@@ -33554,54 +30957,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -33645,89 +31019,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -33771,39 +31096,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the LimitRange",
@@ -33814,54 +31119,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -33905,89 +31181,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34031,39 +31258,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PersistentVolumeClaim",
@@ -34074,54 +31281,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34165,89 +31343,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34291,39 +31420,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Pod",
@@ -34334,54 +31443,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34425,89 +31505,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34551,39 +31582,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PodTemplate",
@@ -34594,54 +31605,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34685,89 +31667,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34811,39 +31744,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ReplicationController",
@@ -34854,54 +31767,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -34945,89 +31829,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35071,39 +31906,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ResourceQuota",
@@ -35114,54 +31929,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35205,89 +31991,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35331,39 +32068,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Secret",
@@ -35374,54 +32091,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35465,89 +32153,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35591,39 +32230,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ServiceAccount",
@@ -35634,54 +32253,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35725,89 +32315,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35851,39 +32392,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Service",
@@ -35894,54 +32415,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -35985,39 +32477,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Namespace",
@@ -36028,46 +32500,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36111,81 +32559,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36229,39 +32633,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Node",
@@ -36272,46 +32656,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36355,81 +32715,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36473,81 +32789,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36591,39 +32863,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PersistentVolume",
@@ -36634,46 +32886,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36717,81 +32945,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36835,81 +33019,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -36953,81 +33093,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -37071,81 +33167,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -37189,81 +33241,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -37307,81 +33315,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -37425,81 +33389,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -37611,18 +33531,10 @@
"operationId": "deleteAdmissionregistrationV1CollectionMutatingWebhookConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -37632,74 +33544,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -37739,74 +33611,34 @@
"operationId": "listAdmissionregistrationV1MutatingWebhookConfiguration",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -37842,11 +33674,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -37872,11 +33700,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -37937,11 +33761,7 @@
"operationId": "deleteAdmissionregistrationV1MutatingWebhookConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -37951,25 +33771,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -38052,11 +33860,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -38070,12 +33874,7 @@
"operationId": "patchAdmissionregistrationV1MutatingWebhookConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -38085,11 +33884,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -38099,11 +33894,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -38164,11 +33955,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -38223,18 +34010,10 @@
"operationId": "deleteAdmissionregistrationV1CollectionValidatingWebhookConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -38244,74 +34023,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -38351,74 +34090,34 @@
"operationId": "listAdmissionregistrationV1ValidatingWebhookConfiguration",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -38454,11 +34153,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -38484,11 +34179,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -38549,11 +34240,7 @@
"operationId": "deleteAdmissionregistrationV1ValidatingWebhookConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -38563,25 +34250,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -38664,11 +34339,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -38682,12 +34353,7 @@
"operationId": "patchAdmissionregistrationV1ValidatingWebhookConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -38697,11 +34363,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -38711,11 +34373,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -38776,11 +34434,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -38866,81 +34520,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -38984,39 +34594,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the MutatingWebhookConfiguration",
@@ -39027,46 +34617,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -39110,81 +34676,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -39228,39 +34750,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ValidatingWebhookConfiguration",
@@ -39271,46 +34773,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -39356,18 +34834,10 @@
"operationId": "deleteAdmissionregistrationV1alpha1CollectionValidatingAdmissionPolicy",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -39377,74 +34847,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -39484,74 +34914,34 @@
"operationId": "listAdmissionregistrationV1alpha1ValidatingAdmissionPolicy",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -39587,11 +34977,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -39617,11 +35003,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -39682,11 +35064,7 @@
"operationId": "deleteAdmissionregistrationV1alpha1ValidatingAdmissionPolicy",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -39696,25 +35074,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -39797,11 +35163,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -39815,12 +35177,7 @@
"operationId": "patchAdmissionregistrationV1alpha1ValidatingAdmissionPolicy",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -39830,11 +35187,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -39844,11 +35197,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -39909,11 +35258,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -40005,11 +35350,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -40023,12 +35364,7 @@
"operationId": "patchAdmissionregistrationV1alpha1ValidatingAdmissionPolicyStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -40038,11 +35374,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -40052,11 +35384,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -40117,11 +35445,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -40176,18 +35500,10 @@
"operationId": "deleteAdmissionregistrationV1alpha1CollectionValidatingAdmissionPolicyBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -40197,74 +35513,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -40304,74 +35580,34 @@
"operationId": "listAdmissionregistrationV1alpha1ValidatingAdmissionPolicyBinding",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -40407,11 +35643,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -40437,11 +35669,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -40502,11 +35730,7 @@
"operationId": "deleteAdmissionregistrationV1alpha1ValidatingAdmissionPolicyBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -40516,25 +35740,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -40617,11 +35829,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -40635,12 +35843,7 @@
"operationId": "patchAdmissionregistrationV1alpha1ValidatingAdmissionPolicyBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -40650,11 +35853,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -40664,11 +35863,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -40729,11 +35924,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -40819,81 +36010,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -40937,39 +36084,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ValidatingAdmissionPolicy",
@@ -40980,46 +36107,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -41063,81 +36166,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -41181,39 +36240,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ValidatingAdmissionPolicyBinding",
@@ -41224,46 +36263,1512 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ },
+ {
+ "$ref": "#/parameters/watch-XNNPZGbK"
+ }
+ ]
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/": {
+ "get": {
+ "consumes": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "description": "get available resources",
+ "operationId": "getAdmissionregistrationV1beta1APIResources",
+ "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": [
+ "admissionregistration_v1beta1"
+ ]
+ }
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies": {
+ "delete": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "delete collection of ValidatingAdmissionPolicy",
+ "operationId": "deleteAdmissionregistrationV1beta1CollectionValidatingAdmissionPolicy",
+ "parameters": [
+ {
+ "$ref": "#/parameters/body-2Y1dVQaQ"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
+ },
+ {
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ }
+ ],
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "deletecollection",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "list or watch objects of kind ValidatingAdmissionPolicy",
+ "operationId": "listAdmissionregistrationV1beta1ValidatingAdmissionPolicy",
+ "parameters": [
+ {
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ },
+ {
+ "$ref": "#/parameters/watch-XNNPZGbK"
+ }
+ ],
+ "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.admissionregistration.v1beta1.ValidatingAdmissionPolicyList"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "list",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ }
+ ],
+ "post": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "create a ValidatingAdmissionPolicy",
+ "operationId": "createAdmissionregistrationV1beta1ValidatingAdmissionPolicy",
+ "parameters": [
+ {
+ "in": "body",
+ "name": "body",
+ "required": true,
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "202": {
+ "description": "Accepted",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "post",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ }
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}": {
+ "delete": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "delete a ValidatingAdmissionPolicy",
+ "operationId": "deleteAdmissionregistrationV1beta1ValidatingAdmissionPolicy",
+ "parameters": [
+ {
+ "$ref": "#/parameters/body-2Y1dVQaQ"
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
+ },
+ {
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
+ },
+ {
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
+ }
+ ],
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "delete",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "read the specified ValidatingAdmissionPolicy",
+ "operationId": "readAdmissionregistrationV1beta1ValidatingAdmissionPolicy",
+ "produces": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "get",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "description": "name of the ValidatingAdmissionPolicy",
+ "in": "path",
+ "name": "name",
+ "required": true,
"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",
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ }
+ ],
+ "patch": {
+ "consumes": [
+ "application/json-patch+json",
+ "application/merge-patch+json",
+ "application/strategic-merge-patch+json",
+ "application/apply-patch+yaml"
+ ],
+ "description": "partially update the specified ValidatingAdmissionPolicy",
+ "operationId": "patchAdmissionregistrationV1beta1ValidatingAdmissionPolicy",
+ "parameters": [
+ {
+ "$ref": "#/parameters/body-78PwaGsr"
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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
+ },
+ {
+ "$ref": "#/parameters/force-tOGGb0Yi"
+ }
+ ],
+ "produces": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "patch",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "put": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "replace the specified ValidatingAdmissionPolicy",
+ "operationId": "replaceAdmissionregistrationV1beta1ValidatingAdmissionPolicy",
+ "parameters": [
+ {
+ "in": "body",
+ "name": "body",
+ "required": true,
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "put",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ }
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}/status": {
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "read status of the specified ValidatingAdmissionPolicy",
+ "operationId": "readAdmissionregistrationV1beta1ValidatingAdmissionPolicyStatus",
+ "produces": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "get",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "description": "name of the ValidatingAdmissionPolicy",
+ "in": "path",
+ "name": "name",
+ "required": true,
"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",
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ }
+ ],
+ "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": "patchAdmissionregistrationV1beta1ValidatingAdmissionPolicyStatus",
+ "parameters": [
+ {
+ "$ref": "#/parameters/body-78PwaGsr"
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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
+ },
+ {
+ "$ref": "#/parameters/force-tOGGb0Yi"
+ }
+ ],
+ "produces": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "patch",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "put": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "replace status of the specified ValidatingAdmissionPolicy",
+ "operationId": "replaceAdmissionregistrationV1beta1ValidatingAdmissionPolicyStatus",
+ "parameters": [
+ {
+ "in": "body",
+ "name": "body",
+ "required": true,
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicy"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "put",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ }
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings": {
+ "delete": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "delete collection of ValidatingAdmissionPolicyBinding",
+ "operationId": "deleteAdmissionregistrationV1beta1CollectionValidatingAdmissionPolicyBinding",
+ "parameters": [
+ {
+ "$ref": "#/parameters/body-2Y1dVQaQ"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
+ },
+ {
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ }
+ ],
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "deletecollection",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ },
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "list or watch objects of kind ValidatingAdmissionPolicyBinding",
+ "operationId": "listAdmissionregistrationV1beta1ValidatingAdmissionPolicyBinding",
+ "parameters": [
+ {
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ },
+ {
+ "$ref": "#/parameters/watch-XNNPZGbK"
+ }
+ ],
+ "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.admissionregistration.v1beta1.ValidatingAdmissionPolicyBindingList"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "list",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ }
+ ],
+ "post": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "create a ValidatingAdmissionPolicyBinding",
+ "operationId": "createAdmissionregistrationV1beta1ValidatingAdmissionPolicyBinding",
+ "parameters": [
+ {
+ "in": "body",
+ "name": "body",
+ "required": true,
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "202": {
+ "description": "Accepted",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "post",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ }
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicybindings/{name}": {
+ "delete": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "delete a ValidatingAdmissionPolicyBinding",
+ "operationId": "deleteAdmissionregistrationV1beta1ValidatingAdmissionPolicyBinding",
+ "parameters": [
+ {
+ "$ref": "#/parameters/body-2Y1dVQaQ"
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
+ },
+ {
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
+ },
+ {
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
+ }
+ ],
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "delete",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ },
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "read the specified ValidatingAdmissionPolicyBinding",
+ "operationId": "readAdmissionregistrationV1beta1ValidatingAdmissionPolicyBinding",
+ "produces": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "get",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "description": "name of the ValidatingAdmissionPolicyBinding",
+ "in": "path",
+ "name": "name",
+ "required": true,
"type": "string",
"uniqueItems": true
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ }
+ ],
+ "patch": {
+ "consumes": [
+ "application/json-patch+json",
+ "application/merge-patch+json",
+ "application/strategic-merge-patch+json",
+ "application/apply-patch+yaml"
+ ],
+ "description": "partially update the specified ValidatingAdmissionPolicyBinding",
+ "operationId": "patchAdmissionregistrationV1beta1ValidatingAdmissionPolicyBinding",
+ "parameters": [
+ {
+ "$ref": "#/parameters/body-78PwaGsr"
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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
+ },
+ {
+ "$ref": "#/parameters/force-tOGGb0Yi"
+ }
+ ],
+ "produces": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "patch",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ },
+ "put": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "replace the specified ValidatingAdmissionPolicyBinding",
+ "operationId": "replaceAdmissionregistrationV1beta1ValidatingAdmissionPolicyBinding",
+ "parameters": [
+ {
+ "in": "body",
+ "name": "body",
+ "required": true,
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ {
+ "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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.admissionregistration.v1beta1.ValidatingAdmissionPolicyBinding"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "put",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ }
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicies": {
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "watch individual changes to a list of ValidatingAdmissionPolicy. deprecated: use the 'watch' parameter with a list operation instead.",
+ "operationId": "watchAdmissionregistrationV1beta1ValidatingAdmissionPolicyList",
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "watchlist",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ },
+ {
+ "$ref": "#/parameters/watch-XNNPZGbK"
+ }
+ ]
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicies/{name}": {
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "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.",
+ "operationId": "watchAdmissionregistrationV1beta1ValidatingAdmissionPolicy",
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "watch",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicy",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "description": "name of the ValidatingAdmissionPolicy",
+ "in": "path",
+ "name": "name",
+ "required": true,
+ "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",
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ },
+ {
+ "$ref": "#/parameters/watch-XNNPZGbK"
+ }
+ ]
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicybindings": {
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "watch individual changes to a list of ValidatingAdmissionPolicyBinding. deprecated: use the 'watch' parameter with a list operation instead.",
+ "operationId": "watchAdmissionregistrationV1beta1ValidatingAdmissionPolicyBindingList",
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "watchlist",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ },
+ {
+ "$ref": "#/parameters/watch-XNNPZGbK"
+ }
+ ]
+ },
+ "/apis/admissionregistration.k8s.io/v1beta1/watch/validatingadmissionpolicybindings/{name}": {
+ "get": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "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.",
+ "operationId": "watchAdmissionregistrationV1beta1ValidatingAdmissionPolicyBinding",
+ "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": [
+ "admissionregistration_v1beta1"
+ ],
+ "x-kubernetes-action": "watch",
+ "x-kubernetes-group-version-kind": {
+ "group": "admissionregistration.k8s.io",
+ "kind": "ValidatingAdmissionPolicyBinding",
+ "version": "v1beta1"
+ }
+ },
+ "parameters": [
+ {
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
+ },
+ {
+ "$ref": "#/parameters/continue-QfD61s0i"
+ },
+ {
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
+ },
+ {
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
+ },
+ {
+ "$ref": "#/parameters/limit-1NfNmdNH"
+ },
+ {
+ "description": "name of the ValidatingAdmissionPolicyBinding",
+ "in": "path",
+ "name": "name",
+ "required": true,
+ "type": "string",
"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
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ },
+ {
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
+ },
+ {
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
+ },
+ {
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
+ },
+ {
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
+ },
+ {
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -41342,18 +37847,10 @@
"operationId": "deleteApiextensionsV1CollectionCustomResourceDefinition",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -41363,74 +37860,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -41470,74 +37927,34 @@
"operationId": "listApiextensionsV1CustomResourceDefinition",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -41573,11 +37990,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -41603,11 +38016,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -41668,11 +38077,7 @@
"operationId": "deleteApiextensionsV1CustomResourceDefinition",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -41682,25 +38087,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -41783,11 +38176,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -41801,12 +38190,7 @@
"operationId": "patchApiextensionsV1CustomResourceDefinition",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -41816,11 +38200,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -41830,11 +38210,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -41895,11 +38271,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -41991,11 +38363,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -42009,12 +38377,7 @@
"operationId": "patchApiextensionsV1CustomResourceDefinitionStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -42024,11 +38387,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -42038,11 +38397,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -42103,11 +38458,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -42193,81 +38544,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -42311,39 +38618,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the CustomResourceDefinition",
@@ -42354,46 +38641,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -42472,18 +38735,10 @@
"operationId": "deleteApiregistrationV1CollectionAPIService",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -42493,74 +38748,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -42600,74 +38815,34 @@
"operationId": "listApiregistrationV1APIService",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -42703,11 +38878,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -42733,11 +38904,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -42798,11 +38965,7 @@
"operationId": "deleteApiregistrationV1APIService",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -42812,25 +38975,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -42913,11 +39064,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -42931,12 +39078,7 @@
"operationId": "patchApiregistrationV1APIService",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -42946,11 +39088,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -42960,11 +39098,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -43025,11 +39159,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -43121,11 +39251,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -43139,12 +39265,7 @@
"operationId": "patchApiregistrationV1APIServiceStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -43154,11 +39275,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -43168,11 +39285,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -43233,11 +39346,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -43323,81 +39432,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -43441,39 +39506,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the APIService",
@@ -43484,46 +39529,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -43633,81 +39654,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -43751,81 +39728,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -43869,81 +39802,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -43956,18 +39845,10 @@
"operationId": "deleteAppsV1CollectionNamespacedControllerRevision",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -43977,74 +39858,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -44084,74 +39925,34 @@
"operationId": "listAppsV1NamespacedControllerRevision",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -44187,19 +39988,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -44225,11 +40017,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -44290,11 +40078,7 @@
"operationId": "deleteAppsV1NamespacedControllerRevision",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -44304,25 +40088,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -44405,19 +40177,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -44431,12 +40194,7 @@
"operationId": "patchAppsV1NamespacedControllerRevision",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -44446,11 +40204,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -44460,11 +40214,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -44525,11 +40275,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -44584,18 +40330,10 @@
"operationId": "deleteAppsV1CollectionNamespacedDaemonSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -44605,74 +40343,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -44712,74 +40410,34 @@
"operationId": "listAppsV1NamespacedDaemonSet",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -44815,19 +40473,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -44853,11 +40502,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -44918,11 +40563,7 @@
"operationId": "deleteAppsV1NamespacedDaemonSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -44932,25 +40573,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -45033,19 +40662,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -45059,12 +40679,7 @@
"operationId": "patchAppsV1NamespacedDaemonSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -45074,11 +40689,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -45088,11 +40699,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -45153,11 +40760,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -45249,19 +40852,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -45275,12 +40869,7 @@
"operationId": "patchAppsV1NamespacedDaemonSetStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -45290,11 +40879,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -45304,11 +40889,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -45369,11 +40950,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -45428,18 +41005,10 @@
"operationId": "deleteAppsV1CollectionNamespacedDeployment",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -45449,74 +41018,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -45556,74 +41085,34 @@
"operationId": "listAppsV1NamespacedDeployment",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -45659,19 +41148,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -45697,11 +41177,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -45762,11 +41238,7 @@
"operationId": "deleteAppsV1NamespacedDeployment",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -45776,25 +41248,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -45877,19 +41337,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -45903,12 +41354,7 @@
"operationId": "patchAppsV1NamespacedDeployment",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -45918,11 +41364,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -45932,11 +41374,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -45997,11 +41435,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -46093,19 +41527,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -46119,12 +41544,7 @@
"operationId": "patchAppsV1NamespacedDeploymentScale",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -46134,11 +41554,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -46148,11 +41564,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -46213,11 +41625,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -46309,19 +41717,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -46335,12 +41734,7 @@
"operationId": "patchAppsV1NamespacedDeploymentStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -46350,11 +41744,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -46364,11 +41754,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -46429,11 +41815,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -46488,18 +41870,10 @@
"operationId": "deleteAppsV1CollectionNamespacedReplicaSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -46509,74 +41883,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -46616,74 +41950,34 @@
"operationId": "listAppsV1NamespacedReplicaSet",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -46719,19 +42013,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -46757,11 +42042,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -46822,11 +42103,7 @@
"operationId": "deleteAppsV1NamespacedReplicaSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -46836,25 +42113,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -46937,19 +42202,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -46963,12 +42219,7 @@
"operationId": "patchAppsV1NamespacedReplicaSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -46978,11 +42229,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -46992,11 +42239,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -47057,11 +42300,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -47153,19 +42392,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -47179,12 +42409,7 @@
"operationId": "patchAppsV1NamespacedReplicaSetScale",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -47194,11 +42419,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -47208,11 +42429,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -47273,11 +42490,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -47369,19 +42582,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -47395,12 +42599,7 @@
"operationId": "patchAppsV1NamespacedReplicaSetStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -47410,11 +42609,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -47424,11 +42619,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -47489,11 +42680,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -47548,18 +42735,10 @@
"operationId": "deleteAppsV1CollectionNamespacedStatefulSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -47569,74 +42748,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -47676,74 +42815,34 @@
"operationId": "listAppsV1NamespacedStatefulSet",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -47779,19 +42878,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -47817,11 +42907,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -47882,11 +42968,7 @@
"operationId": "deleteAppsV1NamespacedStatefulSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -47896,25 +42978,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -47997,19 +43067,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -48023,12 +43084,7 @@
"operationId": "patchAppsV1NamespacedStatefulSet",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -48038,11 +43094,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -48052,11 +43104,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -48117,11 +43165,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -48213,19 +43257,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -48239,12 +43274,7 @@
"operationId": "patchAppsV1NamespacedStatefulSetScale",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -48254,11 +43284,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -48268,11 +43294,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -48333,11 +43355,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -48429,19 +43447,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -48455,12 +43464,7 @@
"operationId": "patchAppsV1NamespacedStatefulSetStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -48470,11 +43474,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -48484,11 +43484,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -48549,11 +43545,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -48639,81 +43631,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -48757,81 +43705,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -48875,81 +43779,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -48993,81 +43853,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -49111,81 +43927,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -49229,89 +44001,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -49355,39 +44078,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ControllerRevision",
@@ -49398,54 +44101,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -49489,89 +44163,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -49615,39 +44240,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the DaemonSet",
@@ -49658,54 +44263,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -49749,89 +44325,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -49875,39 +44402,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Deployment",
@@ -49918,54 +44425,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -50009,89 +44487,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -50135,39 +44564,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ReplicaSet",
@@ -50178,54 +44587,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -50269,89 +44649,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -50395,39 +44726,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the StatefulSet",
@@ -50438,54 +44749,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -50529,81 +44811,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -50647,81 +44885,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -50791,6 +44985,87 @@
]
}
},
+ "/apis/authentication.k8s.io/v1/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
+ },
+ {
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
+ },
+ {
+ "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any 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
+ },
+ {
+ "$ref": "#/parameters/pretty-nN7o5FEq"
+ }
+ ],
+ "post": {
+ "consumes": [
+ "*/*"
+ ],
+ "description": "create a SelfSubjectReview",
+ "operationId": "createAuthenticationV1SelfSubjectReview",
+ "parameters": [
+ {
+ "in": "body",
+ "name": "body",
+ "required": true,
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.authentication.v1.SelfSubjectReview"
+ }
+ }
+ ],
+ "produces": [
+ "application/json",
+ "application/yaml",
+ "application/vnd.kubernetes.protobuf"
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.authentication.v1.SelfSubjectReview"
+ }
+ },
+ "201": {
+ "description": "Created",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.authentication.v1.SelfSubjectReview"
+ }
+ },
+ "202": {
+ "description": "Accepted",
+ "schema": {
+ "$ref": "#/definitions/io.k8s.api.authentication.v1.SelfSubjectReview"
+ }
+ },
+ "401": {
+ "description": "Unauthorized"
+ }
+ },
+ "schemes": [
+ "https"
+ ],
+ "tags": [
+ "authentication_v1"
+ ],
+ "x-kubernetes-action": "post",
+ "x-kubernetes-group-version-kind": {
+ "group": "authentication.k8s.io",
+ "kind": "SelfSubjectReview",
+ "version": "v1"
+ }
+ }
+ },
"/apis/authentication.k8s.io/v1/tokenreviews": {
"parameters": [
{
@@ -50801,11 +45076,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -50815,11 +45086,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -50923,11 +45190,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -50937,11 +45200,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -51045,11 +45304,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -51059,11 +45314,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -51200,11 +45451,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -51214,19 +45461,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -51297,11 +45535,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -51311,11 +45545,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -51386,11 +45616,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -51400,11 +45626,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -51475,11 +45697,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -51489,11 +45707,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -51660,81 +45874,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -51747,18 +45917,10 @@
"operationId": "deleteAutoscalingV1CollectionNamespacedHorizontalPodAutoscaler",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -51768,74 +45930,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -51875,74 +45997,34 @@
"operationId": "listAutoscalingV1NamespacedHorizontalPodAutoscaler",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -51978,19 +46060,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -52016,11 +46089,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -52081,11 +46150,7 @@
"operationId": "deleteAutoscalingV1NamespacedHorizontalPodAutoscaler",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -52095,25 +46160,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -52196,19 +46249,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -52222,12 +46266,7 @@
"operationId": "patchAutoscalingV1NamespacedHorizontalPodAutoscaler",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -52237,11 +46276,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -52251,11 +46286,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -52316,11 +46347,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -52412,19 +46439,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -52438,12 +46456,7 @@
"operationId": "patchAutoscalingV1NamespacedHorizontalPodAutoscalerStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -52453,11 +46466,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -52467,11 +46476,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -52532,11 +46537,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -52622,81 +46623,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -52740,89 +46697,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -52866,39 +46774,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the HorizontalPodAutoscaler",
@@ -52909,54 +46797,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -53033,81 +46892,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -53120,18 +46935,10 @@
"operationId": "deleteAutoscalingV2CollectionNamespacedHorizontalPodAutoscaler",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -53141,74 +46948,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -53248,74 +47015,34 @@
"operationId": "listAutoscalingV2NamespacedHorizontalPodAutoscaler",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -53351,19 +47078,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -53389,11 +47107,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -53454,11 +47168,7 @@
"operationId": "deleteAutoscalingV2NamespacedHorizontalPodAutoscaler",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -53468,25 +47178,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -53569,19 +47267,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -53595,12 +47284,7 @@
"operationId": "patchAutoscalingV2NamespacedHorizontalPodAutoscaler",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -53610,11 +47294,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -53624,11 +47304,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -53689,11 +47365,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -53785,19 +47457,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -53811,12 +47474,7 @@
"operationId": "patchAutoscalingV2NamespacedHorizontalPodAutoscalerStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -53826,11 +47484,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -53840,11 +47494,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -53905,11 +47555,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -53995,81 +47641,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -54113,89 +47715,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -54239,39 +47792,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the HorizontalPodAutoscaler",
@@ -54282,54 +47815,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -54439,81 +47943,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -54557,81 +48017,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -54644,18 +48060,10 @@
"operationId": "deleteBatchV1CollectionNamespacedCronJob",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -54665,74 +48073,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -54772,74 +48140,34 @@
"operationId": "listBatchV1NamespacedCronJob",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -54875,19 +48203,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -54913,11 +48232,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -54978,11 +48293,7 @@
"operationId": "deleteBatchV1NamespacedCronJob",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -54992,25 +48303,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -55093,19 +48392,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -55119,12 +48409,7 @@
"operationId": "patchBatchV1NamespacedCronJob",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -55134,11 +48419,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -55148,11 +48429,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -55213,11 +48490,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -55309,19 +48582,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -55335,12 +48599,7 @@
"operationId": "patchBatchV1NamespacedCronJobStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -55350,11 +48609,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -55364,11 +48619,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -55429,11 +48680,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -55488,18 +48735,10 @@
"operationId": "deleteBatchV1CollectionNamespacedJob",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -55509,74 +48748,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -55616,74 +48815,34 @@
"operationId": "listBatchV1NamespacedJob",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -55719,19 +48878,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -55757,11 +48907,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -55822,11 +48968,7 @@
"operationId": "deleteBatchV1NamespacedJob",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -55836,25 +48978,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -55937,19 +49067,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -55963,12 +49084,7 @@
"operationId": "patchBatchV1NamespacedJob",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -55978,11 +49094,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -55992,11 +49104,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -56057,11 +49165,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -56153,19 +49257,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -56179,12 +49274,7 @@
"operationId": "patchBatchV1NamespacedJobStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -56194,11 +49284,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -56208,11 +49294,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -56273,11 +49355,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -56363,81 +49441,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -56481,81 +49515,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -56599,89 +49589,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -56725,39 +49666,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the CronJob",
@@ -56768,54 +49689,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -56859,89 +49751,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -56985,39 +49828,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Job",
@@ -57028,54 +49851,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -57154,18 +49948,10 @@
"operationId": "deleteCertificatesV1CollectionCertificateSigningRequest",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -57175,74 +49961,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -57282,74 +50028,34 @@
"operationId": "listCertificatesV1CertificateSigningRequest",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -57385,11 +50091,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -57415,11 +50117,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -57480,11 +50178,7 @@
"operationId": "deleteCertificatesV1CertificateSigningRequest",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -57494,25 +50188,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -57595,11 +50277,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -57613,12 +50291,7 @@
"operationId": "patchCertificatesV1CertificateSigningRequest",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -57628,11 +50301,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -57642,11 +50311,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -57707,11 +50372,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -57803,11 +50464,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -57821,12 +50478,7 @@
"operationId": "patchCertificatesV1CertificateSigningRequestApproval",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -57836,11 +50488,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -57850,11 +50498,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -57915,11 +50559,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -58011,11 +50651,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -58029,12 +50665,7 @@
"operationId": "patchCertificatesV1CertificateSigningRequestStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -58044,11 +50675,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -58058,11 +50685,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -58123,11 +50746,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -58213,81 +50832,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -58331,39 +50906,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the CertificateSigningRequest",
@@ -58374,46 +50929,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -58459,18 +50990,10 @@
"operationId": "deleteCertificatesV1alpha1CollectionClusterTrustBundle",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -58480,74 +51003,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -58587,74 +51070,34 @@
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -58690,11 +51133,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -58720,11 +51159,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -58785,11 +51220,7 @@
"operationId": "deleteCertificatesV1alpha1ClusterTrustBundle",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -58799,25 +51230,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -58900,11 +51319,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -58918,12 +51333,7 @@
"operationId": "patchCertificatesV1alpha1ClusterTrustBundle",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -58933,11 +51343,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -58947,11 +51353,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -59012,11 +51414,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -59102,81 +51500,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -59220,39 +51574,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ClusterTrustBundle",
@@ -59263,46 +51597,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -59412,81 +51722,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -59499,18 +51765,10 @@
"operationId": "deleteCoordinationV1CollectionNamespacedLease",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -59520,74 +51778,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -59627,74 +51845,34 @@
"operationId": "listCoordinationV1NamespacedLease",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -59730,19 +51908,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -59768,11 +51937,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -59833,11 +51998,7 @@
"operationId": "deleteCoordinationV1NamespacedLease",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -59847,25 +52008,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -59948,19 +52097,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -59974,12 +52114,7 @@
"operationId": "patchCoordinationV1NamespacedLease",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -59989,11 +52124,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -60003,11 +52134,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -60068,11 +52195,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -60158,81 +52281,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -60276,89 +52355,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -60402,39 +52432,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Lease",
@@ -60445,54 +52455,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -60602,81 +52583,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -60689,18 +52626,10 @@
"operationId": "deleteDiscoveryV1CollectionNamespacedEndpointSlice",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -60710,74 +52639,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -60817,74 +52706,34 @@
"operationId": "listDiscoveryV1NamespacedEndpointSlice",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -60920,19 +52769,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -60958,11 +52798,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -61023,11 +52859,7 @@
"operationId": "deleteDiscoveryV1NamespacedEndpointSlice",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -61037,25 +52869,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -61138,19 +52958,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -61164,12 +52975,7 @@
"operationId": "patchDiscoveryV1NamespacedEndpointSlice",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -61179,11 +52985,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -61193,11 +52995,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -61258,11 +53056,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -61348,81 +53142,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -61466,89 +53216,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -61592,39 +53293,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the EndpointSlice",
@@ -61635,54 +53316,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -61792,81 +53444,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -61879,18 +53487,10 @@
"operationId": "deleteEventsV1CollectionNamespacedEvent",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -61900,74 +53500,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -62007,74 +53567,34 @@
"operationId": "listEventsV1NamespacedEvent",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -62110,19 +53630,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -62148,11 +53659,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -62213,11 +53720,7 @@
"operationId": "deleteEventsV1NamespacedEvent",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -62227,25 +53730,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -62328,19 +53819,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -62354,12 +53836,7 @@
"operationId": "patchEventsV1NamespacedEvent",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -62369,11 +53846,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -62383,11 +53856,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -62448,11 +53917,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -62538,81 +54003,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -62656,89 +54077,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -62782,39 +54154,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Event",
@@ -62825,54 +54177,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -62951,18 +54274,10 @@
"operationId": "deleteFlowcontrolApiserverV1beta2CollectionFlowSchema",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -62972,74 +54287,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -63079,74 +54354,34 @@
"operationId": "listFlowcontrolApiserverV1beta2FlowSchema",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -63182,11 +54417,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -63212,11 +54443,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -63277,11 +54504,7 @@
"operationId": "deleteFlowcontrolApiserverV1beta2FlowSchema",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -63291,25 +54514,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -63392,11 +54603,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -63410,12 +54617,7 @@
"operationId": "patchFlowcontrolApiserverV1beta2FlowSchema",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -63425,11 +54627,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -63439,11 +54637,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -63504,11 +54698,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -63600,11 +54790,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -63618,12 +54804,7 @@
"operationId": "patchFlowcontrolApiserverV1beta2FlowSchemaStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -63633,11 +54814,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -63647,11 +54824,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -63712,11 +54885,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -63771,18 +54940,10 @@
"operationId": "deleteFlowcontrolApiserverV1beta2CollectionPriorityLevelConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -63792,74 +54953,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -63899,74 +55020,34 @@
"operationId": "listFlowcontrolApiserverV1beta2PriorityLevelConfiguration",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -64002,11 +55083,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -64032,11 +55109,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -64097,11 +55170,7 @@
"operationId": "deleteFlowcontrolApiserverV1beta2PriorityLevelConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -64111,25 +55180,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -64212,11 +55269,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -64230,12 +55283,7 @@
"operationId": "patchFlowcontrolApiserverV1beta2PriorityLevelConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -64245,11 +55293,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -64259,11 +55303,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -64324,11 +55364,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -64420,11 +55456,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -64438,12 +55470,7 @@
"operationId": "patchFlowcontrolApiserverV1beta2PriorityLevelConfigurationStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -64453,11 +55480,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -64467,11 +55490,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -64532,11 +55551,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -64622,81 +55637,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -64740,39 +55711,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the FlowSchema",
@@ -64783,46 +55734,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -64866,81 +55793,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -64984,39 +55867,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PriorityLevelConfiguration",
@@ -65027,46 +55890,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -65112,18 +55951,10 @@
"operationId": "deleteFlowcontrolApiserverV1beta3CollectionFlowSchema",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -65133,74 +55964,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -65240,74 +56031,34 @@
"operationId": "listFlowcontrolApiserverV1beta3FlowSchema",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -65343,11 +56094,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -65373,11 +56120,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -65438,11 +56181,7 @@
"operationId": "deleteFlowcontrolApiserverV1beta3FlowSchema",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -65452,25 +56191,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -65553,11 +56280,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -65571,12 +56294,7 @@
"operationId": "patchFlowcontrolApiserverV1beta3FlowSchema",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -65586,11 +56304,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -65600,11 +56314,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -65665,11 +56375,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -65761,11 +56467,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -65779,12 +56481,7 @@
"operationId": "patchFlowcontrolApiserverV1beta3FlowSchemaStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -65794,11 +56491,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -65808,11 +56501,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -65873,11 +56562,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -65932,18 +56617,10 @@
"operationId": "deleteFlowcontrolApiserverV1beta3CollectionPriorityLevelConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -65953,74 +56630,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -66060,74 +56697,34 @@
"operationId": "listFlowcontrolApiserverV1beta3PriorityLevelConfiguration",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -66163,11 +56760,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -66193,11 +56786,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -66258,11 +56847,7 @@
"operationId": "deleteFlowcontrolApiserverV1beta3PriorityLevelConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -66272,25 +56857,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -66373,11 +56946,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -66391,12 +56960,7 @@
"operationId": "patchFlowcontrolApiserverV1beta3PriorityLevelConfiguration",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -66406,11 +56970,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -66420,11 +56980,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -66485,11 +57041,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -66581,11 +57133,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -66599,12 +57147,7 @@
"operationId": "patchFlowcontrolApiserverV1beta3PriorityLevelConfigurationStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -66614,11 +57157,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -66628,11 +57167,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -66693,11 +57228,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -66783,81 +57314,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -66901,39 +57388,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the FlowSchema",
@@ -66944,46 +57411,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -67027,81 +57470,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -67145,39 +57544,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PriorityLevelConfiguration",
@@ -67188,46 +57567,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -67306,18 +57661,10 @@
"operationId": "deleteInternalApiserverV1alpha1CollectionStorageVersion",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -67327,74 +57674,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -67434,74 +57741,34 @@
"operationId": "listInternalApiserverV1alpha1StorageVersion",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -67537,11 +57804,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -67567,11 +57830,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -67632,11 +57891,7 @@
"operationId": "deleteInternalApiserverV1alpha1StorageVersion",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -67646,25 +57901,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -67747,11 +57990,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -67765,12 +58004,7 @@
"operationId": "patchInternalApiserverV1alpha1StorageVersion",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -67780,11 +58014,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -67794,11 +58024,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -67859,11 +58085,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -67955,11 +58177,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -67973,12 +58191,7 @@
"operationId": "patchInternalApiserverV1alpha1StorageVersionStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -67988,11 +58201,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -68002,11 +58211,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -68067,11 +58272,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -68157,81 +58358,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -68275,39 +58432,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the StorageVersion",
@@ -68318,46 +58455,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -68436,18 +58549,10 @@
"operationId": "deleteNetworkingV1CollectionIngressClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -68457,74 +58562,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -68564,74 +58629,34 @@
"operationId": "listNetworkingV1IngressClass",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -68667,11 +58692,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -68697,11 +58718,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -68762,11 +58779,7 @@
"operationId": "deleteNetworkingV1IngressClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -68776,25 +58789,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -68877,11 +58878,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -68895,12 +58892,7 @@
"operationId": "patchNetworkingV1IngressClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -68910,11 +58902,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -68924,11 +58912,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -68989,11 +58973,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -69079,81 +59059,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -69166,18 +59102,10 @@
"operationId": "deleteNetworkingV1CollectionNamespacedIngress",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -69187,74 +59115,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -69294,74 +59182,34 @@
"operationId": "listNetworkingV1NamespacedIngress",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -69397,19 +59245,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -69435,11 +59274,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -69500,11 +59335,7 @@
"operationId": "deleteNetworkingV1NamespacedIngress",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -69514,25 +59345,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -69615,19 +59434,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -69641,12 +59451,7 @@
"operationId": "patchNetworkingV1NamespacedIngress",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -69656,11 +59461,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -69670,11 +59471,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -69735,11 +59532,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -69831,19 +59624,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -69857,12 +59641,7 @@
"operationId": "patchNetworkingV1NamespacedIngressStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -69872,11 +59651,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -69886,11 +59661,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -69951,11 +59722,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -70010,18 +59777,10 @@
"operationId": "deleteNetworkingV1CollectionNamespacedNetworkPolicy",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -70031,74 +59790,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -70138,74 +59857,34 @@
"operationId": "listNetworkingV1NamespacedNetworkPolicy",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -70241,19 +59920,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -70279,11 +59949,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -70344,11 +60010,7 @@
"operationId": "deleteNetworkingV1NamespacedNetworkPolicy",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -70358,25 +60020,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -70459,19 +60109,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -70485,12 +60126,7 @@
"operationId": "patchNetworkingV1NamespacedNetworkPolicy",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -70500,11 +60136,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -70514,11 +60146,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -70579,227 +60207,7 @@
"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.v1.NetworkPolicy"
- }
- },
- "201": {
- "description": "Created",
- "schema": {
- "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicy"
- }
- },
- "401": {
- "description": "Unauthorized"
- }
- },
- "schemes": [
- "https"
- ],
- "tags": [
- "networking_v1"
- ],
- "x-kubernetes-action": "put",
- "x-kubernetes-group-version-kind": {
- "group": "networking.k8s.io",
- "kind": "NetworkPolicy",
- "version": "v1"
- }
- }
- },
- "/apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}/status": {
- "get": {
- "consumes": [
- "*/*"
- ],
- "description": "read status of the specified NetworkPolicy",
- "operationId": "readNetworkingV1NamespacedNetworkPolicyStatus",
- "produces": [
- "application/json",
- "application/yaml",
- "application/vnd.kubernetes.protobuf"
- ],
- "responses": {
- "200": {
- "description": "OK",
- "schema": {
- "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicy"
- }
- },
- "401": {
- "description": "Unauthorized"
- }
- },
- "schemes": [
- "https"
- ],
- "tags": [
- "networking_v1"
- ],
- "x-kubernetes-action": "get",
- "x-kubernetes-group-version-kind": {
- "group": "networking.k8s.io",
- "kind": "NetworkPolicy",
- "version": "v1"
- }
- },
- "parameters": [
- {
- "description": "name of the NetworkPolicy",
- "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 status of the specified NetworkPolicy",
- "operationId": "patchNetworkingV1NamespacedNetworkPolicyStatus",
- "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.v1.NetworkPolicy"
- }
- },
- "201": {
- "description": "Created",
- "schema": {
- "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicy"
- }
- },
- "401": {
- "description": "Unauthorized"
- }
- },
- "schemes": [
- "https"
- ],
- "tags": [
- "networking_v1"
- ],
- "x-kubernetes-action": "patch",
- "x-kubernetes-group-version-kind": {
- "group": "networking.k8s.io",
- "kind": "NetworkPolicy",
- "version": "v1"
- }
- },
- "put": {
- "consumes": [
- "*/*"
- ],
- "description": "replace status of the specified NetworkPolicy",
- "operationId": "replaceNetworkingV1NamespacedNetworkPolicyStatus",
- "parameters": [
- {
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.api.networking.v1.NetworkPolicy"
- }
- },
- {
- "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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -70885,81 +60293,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71003,81 +60367,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71121,39 +60441,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the IngressClass",
@@ -71164,46 +60464,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71247,81 +60523,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71365,89 +60597,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71491,39 +60674,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Ingress",
@@ -71534,54 +60697,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71625,89 +60759,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71751,39 +60836,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the NetworkPolicy",
@@ -71794,54 +60859,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -71885,81 +60921,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -72005,18 +60997,10 @@
"operationId": "deleteNetworkingV1alpha1CollectionClusterCIDR",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -72026,74 +61010,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -72133,74 +61077,34 @@
"operationId": "listNetworkingV1alpha1ClusterCIDR",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -72236,11 +61140,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -72266,11 +61166,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -72331,11 +61227,7 @@
"operationId": "deleteNetworkingV1alpha1ClusterCIDR",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -72345,25 +61237,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -72446,11 +61326,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -72464,12 +61340,7 @@
"operationId": "patchNetworkingV1alpha1ClusterCIDR",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -72479,11 +61350,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -72493,11 +61360,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -72558,11 +61421,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -72617,18 +61476,10 @@
"operationId": "deleteNetworkingV1alpha1CollectionIPAddress",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -72638,74 +61489,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -72745,74 +61556,34 @@
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -72848,11 +61619,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -72878,11 +61645,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -72943,11 +61706,7 @@
"operationId": "deleteNetworkingV1alpha1IPAddress",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -72957,25 +61716,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -73058,11 +61805,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -73076,12 +61819,7 @@
"operationId": "patchNetworkingV1alpha1IPAddress",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -73091,11 +61829,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -73105,11 +61839,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -73170,11 +61900,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -73260,81 +61986,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -73378,39 +62060,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ClusterCIDR",
@@ -73421,46 +62083,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -73504,81 +62142,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -73622,39 +62216,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the IPAddress",
@@ -73665,46 +62239,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -73783,18 +62333,10 @@
"operationId": "deleteNodeV1CollectionRuntimeClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -73804,74 +62346,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -73911,74 +62413,34 @@
"operationId": "listNodeV1RuntimeClass",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -74014,11 +62476,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -74044,11 +62502,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -74109,11 +62563,7 @@
"operationId": "deleteNodeV1RuntimeClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -74123,25 +62573,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -74224,11 +62662,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -74242,12 +62676,7 @@
"operationId": "patchNodeV1RuntimeClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -74257,11 +62686,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -74271,11 +62696,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -74336,11 +62757,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -74426,81 +62843,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -74544,39 +62917,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the RuntimeClass",
@@ -74587,46 +62940,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -74705,18 +63034,10 @@
"operationId": "deletePolicyV1CollectionNamespacedPodDisruptionBudget",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -74726,74 +63047,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -74833,74 +63114,34 @@
"operationId": "listPolicyV1NamespacedPodDisruptionBudget",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -74936,19 +63177,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -74974,11 +63206,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -75039,11 +63267,7 @@
"operationId": "deletePolicyV1NamespacedPodDisruptionBudget",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -75053,25 +63277,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -75154,19 +63366,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -75180,12 +63383,7 @@
"operationId": "patchPolicyV1NamespacedPodDisruptionBudget",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -75195,11 +63393,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -75209,11 +63403,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -75274,11 +63464,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -75370,19 +63556,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -75396,12 +63573,7 @@
"operationId": "patchPolicyV1NamespacedPodDisruptionBudgetStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -75411,11 +63583,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -75425,11 +63593,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -75490,11 +63654,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -75580,81 +63740,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -75698,89 +63814,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -75824,39 +63891,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PodDisruptionBudget",
@@ -75867,54 +63914,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -75958,81 +63976,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -76111,18 +64085,10 @@
"operationId": "deleteRbacAuthorizationV1CollectionClusterRoleBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -76132,74 +64098,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -76239,74 +64165,34 @@
"operationId": "listRbacAuthorizationV1ClusterRoleBinding",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -76342,11 +64228,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -76372,11 +64254,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -76437,11 +64315,7 @@
"operationId": "deleteRbacAuthorizationV1ClusterRoleBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -76451,25 +64325,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -76552,11 +64414,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -76570,12 +64428,7 @@
"operationId": "patchRbacAuthorizationV1ClusterRoleBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -76585,11 +64438,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -76599,11 +64448,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -76664,11 +64509,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -76723,18 +64564,10 @@
"operationId": "deleteRbacAuthorizationV1CollectionClusterRole",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -76744,74 +64577,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -76851,74 +64644,34 @@
"operationId": "listRbacAuthorizationV1ClusterRole",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -76954,11 +64707,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -76984,11 +64733,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -77049,11 +64794,7 @@
"operationId": "deleteRbacAuthorizationV1ClusterRole",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -77063,25 +64804,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -77164,11 +64893,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -77182,12 +64907,7 @@
"operationId": "patchRbacAuthorizationV1ClusterRole",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -77197,11 +64917,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -77211,11 +64927,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -77276,11 +64988,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -77335,18 +65043,10 @@
"operationId": "deleteRbacAuthorizationV1CollectionNamespacedRoleBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -77356,74 +65056,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -77463,74 +65123,34 @@
"operationId": "listRbacAuthorizationV1NamespacedRoleBinding",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -77566,19 +65186,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -77604,11 +65215,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -77669,11 +65276,7 @@
"operationId": "deleteRbacAuthorizationV1NamespacedRoleBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -77683,25 +65286,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -77784,19 +65375,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -77810,12 +65392,7 @@
"operationId": "patchRbacAuthorizationV1NamespacedRoleBinding",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -77825,11 +65402,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -77839,11 +65412,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -77904,11 +65473,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -77963,18 +65528,10 @@
"operationId": "deleteRbacAuthorizationV1CollectionNamespacedRole",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -77984,74 +65541,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -78091,74 +65608,34 @@
"operationId": "listRbacAuthorizationV1NamespacedRole",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -78194,19 +65671,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -78232,11 +65700,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -78297,11 +65761,7 @@
"operationId": "deleteRbacAuthorizationV1NamespacedRole",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -78311,25 +65771,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -78412,19 +65860,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -78438,12 +65877,7 @@
"operationId": "patchRbacAuthorizationV1NamespacedRole",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -78453,11 +65887,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -78467,11 +65897,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -78532,11 +65958,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -78622,81 +66044,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -78740,81 +66118,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -78858,81 +66192,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -78976,39 +66266,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ClusterRoleBinding",
@@ -79019,46 +66289,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79102,81 +66348,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79220,39 +66422,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ClusterRole",
@@ -79263,46 +66445,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79346,89 +66504,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79472,39 +66581,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the RoleBinding",
@@ -79515,54 +66604,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79606,89 +66666,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79732,39 +66743,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the Role",
@@ -79775,54 +66766,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79866,81 +66828,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -79984,81 +66902,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -80137,18 +67011,10 @@
"operationId": "deleteResourceV1alpha2CollectionNamespacedPodSchedulingContext",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -80158,74 +67024,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -80265,74 +67091,34 @@
"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.",
- "in": "query",
- "name": "allowWatchBookmarks",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -80368,19 +67154,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -80406,11 +67183,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -80471,11 +67244,7 @@
"operationId": "deleteResourceV1alpha2NamespacedPodSchedulingContext",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -80485,25 +67254,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -80586,19 +67343,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -80612,12 +67360,7 @@
"operationId": "patchResourceV1alpha2NamespacedPodSchedulingContext",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -80627,11 +67370,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -80641,11 +67380,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -80706,11 +67441,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -80802,19 +67533,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -80828,12 +67550,7 @@
"operationId": "patchResourceV1alpha2NamespacedPodSchedulingContextStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -80843,11 +67560,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -80857,11 +67570,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -80922,11 +67631,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -80981,18 +67686,10 @@
"operationId": "deleteResourceV1alpha2CollectionNamespacedResourceClaim",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -81002,74 +67699,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -81109,74 +67766,34 @@
"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.",
- "in": "query",
- "name": "allowWatchBookmarks",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -81212,19 +67829,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -81250,11 +67858,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -81315,11 +67919,7 @@
"operationId": "deleteResourceV1alpha2NamespacedResourceClaim",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -81329,25 +67929,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -81430,19 +68018,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -81456,12 +68035,7 @@
"operationId": "patchResourceV1alpha2NamespacedResourceClaim",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -81471,11 +68045,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -81485,11 +68055,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -81550,11 +68116,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -81646,19 +68208,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -81672,12 +68225,7 @@
"operationId": "patchResourceV1alpha2NamespacedResourceClaimStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -81687,11 +68235,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -81701,11 +68245,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -81766,11 +68306,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -81825,18 +68361,10 @@
"operationId": "deleteResourceV1alpha2CollectionNamespacedResourceClaimTemplate",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -81846,74 +68374,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -81953,74 +68441,34 @@
"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.",
- "in": "query",
- "name": "allowWatchBookmarks",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -82056,19 +68504,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -82094,11 +68533,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -82159,11 +68594,7 @@
"operationId": "deleteResourceV1alpha2NamespacedResourceClaimTemplate",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -82173,25 +68604,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -82274,19 +68693,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -82300,12 +68710,7 @@
"operationId": "patchResourceV1alpha2NamespacedResourceClaimTemplate",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -82315,11 +68720,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -82329,11 +68730,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -82394,11 +68791,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -82484,81 +68877,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -82602,81 +68951,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -82720,81 +69025,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -82807,18 +69068,10 @@
"operationId": "deleteResourceV1alpha2CollectionResourceClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -82828,74 +69081,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -82935,74 +69148,34 @@
"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.",
- "in": "query",
- "name": "allowWatchBookmarks",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -83038,11 +69211,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -83068,11 +69237,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -83133,11 +69298,7 @@
"operationId": "deleteResourceV1alpha2ResourceClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -83147,25 +69308,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -83248,11 +69397,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -83266,12 +69411,7 @@
"operationId": "patchResourceV1alpha2ResourceClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -83281,11 +69421,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -83295,11 +69431,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -83360,11 +69492,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -83450,89 +69578,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -83576,39 +69655,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PodSchedulingContext",
@@ -83619,54 +69678,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -83710,89 +69740,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -83836,39 +69817,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ResourceClaim",
@@ -83879,54 +69840,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -83970,89 +69902,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -84096,39 +69979,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ResourceClaimTemplate",
@@ -84139,54 +70002,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -84230,81 +70064,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -84348,81 +70138,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -84466,81 +70212,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -84584,81 +70286,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -84702,39 +70360,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the ResourceClass",
@@ -84745,46 +70383,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -84863,18 +70477,10 @@
"operationId": "deleteSchedulingV1CollectionPriorityClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -84884,74 +70490,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -84991,74 +70557,34 @@
"operationId": "listSchedulingV1PriorityClass",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -85094,11 +70620,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -85124,11 +70646,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -85189,11 +70707,7 @@
"operationId": "deleteSchedulingV1PriorityClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -85203,25 +70717,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -85304,11 +70806,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -85322,12 +70820,7 @@
"operationId": "patchSchedulingV1PriorityClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -85337,11 +70830,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -85351,11 +70840,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -85416,11 +70901,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -85506,81 +70987,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -85624,39 +71061,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the PriorityClass",
@@ -85667,46 +71084,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -85785,18 +71178,10 @@
"operationId": "deleteStorageV1CollectionCSIDriver",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -85806,74 +71191,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -85913,74 +71258,34 @@
"operationId": "listStorageV1CSIDriver",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -86016,11 +71321,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -86046,11 +71347,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -86111,11 +71408,7 @@
"operationId": "deleteStorageV1CSIDriver",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -86125,25 +71418,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -86226,11 +71507,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -86244,12 +71521,7 @@
"operationId": "patchStorageV1CSIDriver",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -86259,11 +71531,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -86273,11 +71541,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -86338,11 +71602,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -86397,18 +71657,10 @@
"operationId": "deleteStorageV1CollectionCSINode",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -86418,74 +71670,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -86525,74 +71737,34 @@
"operationId": "listStorageV1CSINode",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -86628,11 +71800,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -86658,11 +71826,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -86723,11 +71887,7 @@
"operationId": "deleteStorageV1CSINode",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -86737,25 +71897,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -86838,11 +71986,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -86856,12 +72000,7 @@
"operationId": "patchStorageV1CSINode",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -86871,11 +72010,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -86885,11 +72020,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -86950,11 +72081,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -87040,81 +72167,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -87127,18 +72210,10 @@
"operationId": "deleteStorageV1CollectionNamespacedCSIStorageCapacity",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -87148,74 +72223,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -87255,74 +72290,34 @@
"operationId": "listStorageV1NamespacedCSIStorageCapacity",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -87358,19 +72353,10 @@
},
"parameters": [
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -87396,11 +72382,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -87461,11 +72443,7 @@
"operationId": "deleteStorageV1NamespacedCSIStorageCapacity",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -87475,25 +72453,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -87576,19 +72542,10 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -87602,12 +72559,7 @@
"operationId": "patchStorageV1NamespacedCSIStorageCapacity",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -87617,11 +72569,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -87631,11 +72579,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -87696,11 +72640,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -87755,18 +72695,10 @@
"operationId": "deleteStorageV1CollectionStorageClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -87776,74 +72708,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -87883,74 +72775,34 @@
"operationId": "listStorageV1StorageClass",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -87986,11 +72838,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -88016,11 +72864,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -88081,11 +72925,7 @@
"operationId": "deleteStorageV1StorageClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -88095,25 +72935,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -88196,11 +73024,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -88214,12 +73038,7 @@
"operationId": "patchStorageV1StorageClass",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -88229,11 +73048,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -88243,11 +73058,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -88308,11 +73119,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -88367,18 +73174,10 @@
"operationId": "deleteStorageV1CollectionVolumeAttachment",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
"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",
@@ -88388,74 +73187,34 @@
"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
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
}
],
"produces": [
@@ -88495,74 +73254,34 @@
"operationId": "listStorageV1VolumeAttachment",
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
],
"produces": [
@@ -88598,11 +73317,7 @@
},
"parameters": [
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"post": {
@@ -88628,11 +73343,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -88693,11 +73404,7 @@
"operationId": "deleteStorageV1VolumeAttachment",
"parameters": [
{
- "in": "body",
- "name": "body",
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions"
- }
+ "$ref": "#/parameters/body-2Y1dVQaQ"
},
{
"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",
@@ -88707,25 +73414,13 @@
"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
+ "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS"
},
{
- "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
+ "$ref": "#/parameters/orphanDependents-uRB25kX5"
},
{
- "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
+ "$ref": "#/parameters/propagationPolicy-6jk3prlO"
}
],
"produces": [
@@ -88808,11 +73503,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -88826,12 +73517,7 @@
"operationId": "patchStorageV1VolumeAttachment",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -88841,11 +73527,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -88855,11 +73537,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -88920,11 +73598,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -89016,11 +73690,7 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
}
],
"patch": {
@@ -89034,12 +73704,7 @@
"operationId": "patchStorageV1VolumeAttachmentStatus",
"parameters": [
{
- "in": "body",
- "name": "body",
- "required": true,
- "schema": {
- "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Patch"
- }
+ "$ref": "#/parameters/body-78PwaGsr"
},
{
"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",
@@ -89049,11 +73714,7 @@
"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
+ "$ref": "#/parameters/fieldManager-7c6nTn1T"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -89063,11 +73724,7 @@
"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
+ "$ref": "#/parameters/force-tOGGb0Yi"
}
],
"produces": [
@@ -89128,11 +73785,7 @@
"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
+ "$ref": "#/parameters/fieldManager-Qy4HdaTW"
},
{
"description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.",
@@ -89218,81 +73871,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -89336,39 +73945,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the CSIDriver",
@@ -89379,46 +73968,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -89462,81 +74027,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -89580,39 +74101,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the CSINode",
@@ -89623,46 +74124,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -89706,81 +74183,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -89824,89 +74257,40 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -89950,39 +74334,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the CSIStorageCapacity",
@@ -89993,54 +74357,25 @@
"uniqueItems": true
},
{
- "description": "object name and auth scope, such as for teams and projects",
- "in": "path",
- "name": "namespace",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/namespace-vgWSWtn3"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -90084,81 +74419,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -90202,39 +74493,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the StorageClass",
@@ -90245,46 +74516,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -90328,81 +74575,37 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -90446,39 +74649,19 @@
},
"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
+ "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J"
},
{
- "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
+ "$ref": "#/parameters/continue-QfD61s0i"
},
{
- "description": "A selector to restrict the list of returned objects by their fields. Defaults to everything.",
- "in": "query",
- "name": "fieldSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/fieldSelector-xIcQKXFG"
},
{
- "description": "A selector to restrict the list of returned objects by their labels. Defaults to everything.",
- "in": "query",
- "name": "labelSelector",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/labelSelector-5Zw57w4C"
},
{
- "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
+ "$ref": "#/parameters/limit-1NfNmdNH"
},
{
"description": "name of the VolumeAttachment",
@@ -90489,46 +74672,22 @@
"uniqueItems": true
},
{
- "description": "If 'true', then the output is pretty printed.",
- "in": "query",
- "name": "pretty",
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/pretty-nN7o5FEq"
},
{
- "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
+ "$ref": "#/parameters/resourceVersion-5WAnf1kx"
},
{
- "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
+ "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC"
},
{
- "description": "`sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"k8s.io/initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan\n is interpreted as \"data at least as new as the provided `resourceVersion`\"\n and the bookmark event is send when the state is synced\n to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n bookmark event is send when the state is synced at least to the moment\n when request started being processed.\n- `resourceVersionMatch` set to any other value or unset\n Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise.",
- "in": "query",
- "name": "sendInitialEvents",
- "type": "boolean",
- "uniqueItems": true
+ "$ref": "#/parameters/sendInitialEvents-rLXlEK_k"
},
{
- "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
+ "$ref": "#/parameters/timeoutSeconds-yvYezaOC"
},
{
- "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
+ "$ref": "#/parameters/watch-XNNPZGbK"
}
]
},
@@ -90565,12 +74724,7 @@
},
"parameters": [
{
- "description": "path to the log",
- "in": "path",
- "name": "logpath",
- "required": true,
- "type": "string",
- "uniqueItems": true
+ "$ref": "#/parameters/logpath-Noq7euwC"
}
]
},
diff --git a/api-ref-assets/config/fields.yaml b/api-ref-assets/config/fields.yaml
index 4f78cffcf7..f39deef600 100644
--- a/api-ref-assets/config/fields.yaml
+++ b/api-ref-assets/config/fields.yaml
@@ -88,6 +88,7 @@
- fields:
- nominatedNodeName
- hostIP
+ - hostIPs
- startTime
- phase
- message
@@ -99,6 +100,7 @@
- initContainerStatuses
- containerStatuses
- ephemeralContainerStatuses
+ - resourceClaimStatuses
- resize
- definition: io.k8s.api.core.v1.Container
@@ -137,6 +139,7 @@
- livenessProbe
- readinessProbe
- startupProbe
+ - restartPolicy
- name: Security Context
fields:
- securityContext
@@ -228,6 +231,7 @@
fields:
- terminationMessagePath
- terminationMessagePolicy
+ - restartPolicy
- name: Debugging
fields:
- stdin
@@ -393,9 +397,14 @@
fields:
- selector
- manualSelector
- - name: Alpha level
+ - name: Beta level
fields:
- podFailurePolicy
+ - name: Alpha level
+ fields:
+ - backoffLimitPerIndex
+ - maxFailedIndexes
+ - podReplacementPolicy
- definition: io.k8s.api.batch.v1.JobStatus
field_categories:
@@ -411,6 +420,10 @@
- name: Beta level
fields:
- ready
+ - name: Alpha level
+ fields:
+ - failedIndexes
+ - terminating
- definition: io.k8s.api.batch.v1.CronJobSpec
field_categories:
diff --git a/api-ref-assets/config/toc.yaml b/api-ref-assets/config/toc.yaml
index 77bd3cbe9d..a53e2d1b8b 100644
--- a/api-ref-assets/config/toc.yaml
+++ b/api-ref-assets/config/toc.yaml
@@ -153,7 +153,7 @@ parts:
version: v1alpha1
- name: SelfSubjectReview
group: authentication.k8s.io
- version: v1beta1
+ version: v1
- name: Authorization Resources
chapters:
- name: LocalSubjectAccessReview
@@ -168,9 +168,6 @@ parts:
- name: SubjectAccessReview
group: authorization.k8s.io
version: v1
- - name: SelfSubjectReview
- group: authentication.k8s.io
- version: v1alpha1
- name: ClusterRole
group: rbac.authorization.k8s.io
version: v1
@@ -218,7 +215,7 @@ parts:
version: v1
- name: ValidatingAdmissionPolicy
group: admissionregistration.k8s.io
- version: v1alpha1
+ version: v1beta1
otherDefinitions:
- ValidatingAdmissionPolicyList
- ValidatingAdmissionPolicyBinding
From 1e2ed8874383434fda20a97becf3c74989a80869 Mon Sep 17 00:00:00 2001
From: Philippe Martin
Date: Wed, 26 Jul 2023 13:45:06 +0200
Subject: [PATCH 094/446] Generated content
---
...w-v1beta1.md => self-subject-review-v1.md} | 24 +--
.../cluster-role-binding-v1.md | 4 +-
.../cluster-role-v1.md | 2 +-
.../role-binding-v1.md | 4 +-
.../authorization-resources/role-v1.md | 2 +-
.../self-subject-review-v1alpha1.md | 142 -------------
.../priority-level-configuration-v1beta3.md | 25 ++-
.../common-definitions/label-selector.md | 2 -
.../persistent-volume-claim-v1.md | 49 ++++-
.../persistent-volume-v1.md | 7 +
.../custom-resource-definition-v1.md | 8 +
.../mutating-webhook-configuration-v1.md | 2 +-
...=> validating-admission-policy-v1beta1.md} | 135 ++++++++----
.../validating-webhook-configuration-v1.md | 2 +-
...-admission-policy-binding-list-v1beta1.md} | 10 +-
.../policy-resources/network-policy-v1.md | 200 ------------------
.../service-resources/endpoint-slice-v1.md | 2 +
.../service-resources/endpoints-v1.md | 2 +
.../service-resources/service-v1.md | 17 +-
.../workload-resources/job-v1.md | 41 +++-
.../workload-resources/pod-v1.md | 72 +++++--
21 files changed, 314 insertions(+), 438 deletions(-)
rename content/en/docs/reference/kubernetes-api/authentication-resources/{self-subject-review-v1beta1.md => self-subject-review-v1.md} (83%)
delete mode 100644 content/en/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
rename content/en/docs/reference/kubernetes-api/extend-resources/{validating-admission-policy-v1alpha1.md => validating-admission-policy-v1beta1.md} (87%)
rename content/en/docs/reference/kubernetes-api/other-resources/{validating-admission-policy-binding-list-v1alpha1.md => validating-admission-policy-binding-list-v1beta1.md} (73%)
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-v1.md
similarity index 83%
rename from content/en/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1beta1.md
rename to content/en/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1.md
index 064d3f8f02..5137fb84b8 100644
--- 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-v1.md
@@ -1,11 +1,11 @@
---
api_metadata:
- apiVersion: "authentication.k8s.io/v1beta1"
- import: "k8s.io/api/authentication/v1beta1"
+ apiVersion: "authentication.k8s.io/v1"
+ import: "k8s.io/api/authentication/v1"
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"
+title: "SelfSubjectReview"
weight: 6
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: authentication.k8s.io/v1beta1`
+`apiVersion: authentication.k8s.io/v1`
-`import "k8s.io/api/authentication/v1beta1"`
+`import "k8s.io/api/authentication/v1"`
## SelfSubjectReview {#SelfSubjectReview}
@@ -32,7 +32,7 @@ SelfSubjectReview contains the user information that the kube-apiserver has abou
-- **apiVersion**: authentication.k8s.io/v1beta1
+- **apiVersion**: authentication.k8s.io/v1
- **kind**: SelfSubjectReview
@@ -42,7 +42,7 @@ SelfSubjectReview contains the user information that the kube-apiserver has abou
Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
-- **status** (}}">SelfSubjectReviewStatus)
+- **status** (}}">SelfSubjectReviewStatus)
Status is filled in by the server with the user attributes.
@@ -98,12 +98,12 @@ SelfSubjectReviewStatus is filled by the kube-apiserver and sent back to a user.
#### HTTP Request
-POST /apis/authentication.k8s.io/v1beta1/selfsubjectreviews
+POST /apis/authentication.k8s.io/v1/selfsubjectreviews
#### Parameters
-- **body**: }}">SelfSubjectReview, required
+- **body**: }}">SelfSubjectReview, required
@@ -132,11 +132,11 @@ POST /apis/authentication.k8s.io/v1beta1/selfsubjectreviews
#### Response
-200 (}}">SelfSubjectReview): OK
+200 (}}">SelfSubjectReview): OK
-201 (}}">SelfSubjectReview): Created
+201 (}}">SelfSubjectReview): Created
-202 (}}">SelfSubjectReview): Accepted
+202 (}}">SelfSubjectReview): Accepted
401: Unauthorized
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 f84ba0fcf6..63016f9d10 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
@@ -6,7 +6,7 @@ api_metadata:
content_type: "api_reference"
description: "ClusterRoleBinding references a ClusterRole, but not contain it."
title: "ClusterRoleBinding"
-weight: 7
+weight: 6
auto_generated: true
---
@@ -44,7 +44,7 @@ ClusterRoleBinding references a ClusterRole, but not contain it. It can referen
- **roleRef** (RoleRef), required
- RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.
+ RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error. This field is immutable.
*RoleRef contains information that points to the role being used*
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 b7e87bf0cc..5a4805c682 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
@@ -6,7 +6,7 @@ api_metadata:
content_type: "api_reference"
description: "ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding."
title: "ClusterRole"
-weight: 6
+weight: 5
auto_generated: true
---
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 75d4d5f0f8..6d26ada485 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
@@ -6,7 +6,7 @@ api_metadata:
content_type: "api_reference"
description: "RoleBinding references a role, but does not contain it."
title: "RoleBinding"
-weight: 9
+weight: 8
auto_generated: true
---
@@ -44,7 +44,7 @@ RoleBinding references a role, but does not contain it. It can reference a Role
- **roleRef** (RoleRef), required
- 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.
+ 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. This field is immutable.
*RoleRef contains information that points to the role being used*
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 6b378be7ca..6985e4fca9 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
@@ -6,7 +6,7 @@ api_metadata:
content_type: "api_reference"
description: "Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding."
title: "Role"
-weight: 8
+weight: 7
auto_generated: true
---
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
deleted file mode 100644
index a8ed8464f2..0000000000
--- a/content/en/docs/reference/kubernetes-api/authorization-resources/self-subject-review-v1alpha1.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-api_metadata:
- apiVersion: "authentication.k8s.io/v1alpha1"
- import: "k8s.io/api/authentication/v1alpha1"
- 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 v1alpha1"
-weight: 5
-auto_generated: true
----
-
-
-
-`apiVersion: authentication.k8s.io/v1alpha1`
-
-`import "k8s.io/api/authentication/v1alpha1"`
-
-
-## 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.
-
-
-
-- **apiVersion**: authentication.k8s.io/v1alpha1
-
-
-- **kind**: SelfSubjectReview
-
-
-- **metadata** (}}">ObjectMeta)
-
- Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
-
-- **status** (}}">SelfSubjectReviewStatus)
-
- 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.
-
-
-
-- **userInfo** (UserInfo)
-
- User attributes of the user making this request.
-
-
- *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}
-
-
-
-
-
-
-
-
-
-
-### `create` create a SelfSubjectReview
-
-#### HTTP Request
-
-POST /apis/authentication.k8s.io/v1alpha1/selfsubjectreviews
-
-#### Parameters
-
-
-- **body**: }}">SelfSubjectReview, required
-
-
-
-
-- **dryRun** (*in query*): string
-
- }}">dryRun
-
-
-- **fieldManager** (*in query*): string
-
- }}">fieldManager
-
-
-- **fieldValidation** (*in query*): string
-
- }}">fieldValidation
-
-
-- **pretty** (*in query*): string
-
- }}">pretty
-
-
-
-#### Response
-
-
-200 (}}">SelfSubjectReview): OK
-
-201 (}}">SelfSubjectReview): Created
-
-202 (}}">SelfSubjectReview): Accepted
-
-401: Unauthorized
-
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 420699dfaf..a5a54c354f 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
@@ -64,6 +64,27 @@ PriorityLevelConfigurationSpec specifies the configuration of a priority level.
`type` indicates whether this priority level is subject to limitation on request execution. A value of `"Exempt"` 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 `"Limited"` means that (a) requests of this priority level _are_ subject to limits and (b) some of the server's limited capacity is made available exclusively to this priority level. Required.
+- **exempt** (ExemptPriorityLevelConfiguration)
+
+ `exempt` specifies how requests are handled for an exempt priority level. This field MUST be empty if `type` is `"Limited"`. This field MAY be non-empty if `type` is `"Exempt"`. If empty and `type` is `"Exempt"` then the default values for `ExemptPriorityLevelConfiguration` apply.
+
+
+ *ExemptPriorityLevelConfiguration describes the configurable aspects of the handling of exempt requests. In the mandatory exempt configuration object the values in the fields here can be modified by authorized users, unlike the rest of the `spec`.*
+
+ - **exempt.lendablePercent** (int32)
+
+ `lendablePercent` prescribes the fraction of the level's NominalCL that can be borrowed by other priority levels. This 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's LendableConcurrencyLimit (LendableCL), is defined as follows.
+
+ LendableCL(i) = round( NominalCL(i) * lendablePercent(i)/100.0 )
+
+ - **exempt.nominalConcurrencyShares** (int32)
+
+ `nominalConcurrencyShares` (NCS) contributes to the computation of the NominalConcurrencyLimit (NominalCL) of this level. This is the number of execution seats nominally reserved for this priority level. This DOES NOT limit the dispatching from this priority level but affects the other priority levels through the borrowing mechanism. The server's concurrency limit (ServerCL) is divided among all the priority levels in proportion to their NCS values:
+
+ NominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[priority level k] NCS(k)
+
+ Bigger numbers mean a larger nominal concurrency limit, at the expense of every other priority level. This field has a default value of zero.
+
- **limited** (LimitedPriorityLevelConfiguration)
`limited` specifies how requests are handled for a Limited priority level. This field must be non-empty if and only if `type` is `"Limited"`.
@@ -121,9 +142,9 @@ PriorityLevelConfigurationSpec specifies the configuration of a priority level.
`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'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)
+ NominalCL(i) = ceil( ServerCL * NCS(i) / sum_ncs ) sum_ncs = sum[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.
+ Bigger numbers mean a larger nominal concurrency limit, at the expense of every other priority level. This field has a default value of 30.
diff --git a/content/en/docs/reference/kubernetes-api/common-definitions/label-selector.md b/content/en/docs/reference/kubernetes-api/common-definitions/label-selector.md
index d81c26d17a..8569c661d7 100644
--- a/content/en/docs/reference/kubernetes-api/common-definitions/label-selector.md
+++ b/content/en/docs/reference/kubernetes-api/common-definitions/label-selector.md
@@ -39,8 +39,6 @@ A label selector is a label query over a set of resources. The result of matchLa
- **matchExpressions.key** (string), required
- *Patch strategy: merge on key `key`*
-
key is the label key that the selector applies to.
- **matchExpressions.operator** (string), required
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 4fc8f3aa65..a7a3c475bd 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
@@ -163,9 +163,52 @@ PersistentVolumeClaimStatus is the current status of a persistent volume claim.
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
+- **allocatedResourceStatuses** (map[string]string)
+
+ allocatedResourceStatuses stores status of resource being resized for the given PVC. Key names follow standard Kubernetes label syntax. Valid values are either:
+ * Un-prefixed keys:
+ - storage - the capacity of the volume.
+ * Custom resources must use implementation-defined prefixed names such as "example.com/my-custom-resource"
+ Apart from above values - keys that are unprefixed or have kubernetes.io prefix are considered reserved and hence may not be used.
+
+ ClaimResourceStatus can be in any of following states:
+ - ControllerResizeInProgress:
+ State set when resize controller starts resizing the volume in control-plane.
+ - ControllerResizeFailed:
+ State set when resize has failed in resize controller with a terminal error.
+ - NodeResizePending:
+ State set when resize controller has finished resizing the volume but further resizing of
+ volume is needed on the node.
+ - NodeResizeInProgress:
+ State set when kubelet starts resizing the volume.
+ - NodeResizeFailed:
+ State set when resizing has failed in kubelet with a terminal error. Transient errors don't set
+ NodeResizeFailed.
+ For example: if expanding a PVC for more capacity - this field can be one of the following states:
+ - pvc.status.allocatedResourceStatus['storage'] = "ControllerResizeInProgress"
+ - pvc.status.allocatedResourceStatus['storage'] = "ControllerResizeFailed"
+ - pvc.status.allocatedResourceStatus['storage'] = "NodeResizePending"
+ - pvc.status.allocatedResourceStatus['storage'] = "NodeResizeInProgress"
+ - pvc.status.allocatedResourceStatus['storage'] = "NodeResizeFailed"
+ When this field is not set, it means that no resize operation is in progress for the given PVC.
+
+ A controller that receives PVC update with previously unknown resourceName or ClaimResourceStatus should ignore the update for the purpose it was designed. For example - a controller that only is responsible for resizing capacity of the volume, should ignore PVC updates that change other valid resources associated with PVC.
+
+ This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.
+
- **allocatedResources** (map[string]}}">Quantity)
- 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.
+ allocatedResources tracks the resources allocated to a PVC including its capacity. Key names follow standard Kubernetes label syntax. Valid values are either:
+ * Un-prefixed keys:
+ - storage - the capacity of the volume.
+ * Custom resources must use implementation-defined prefixed names such as "example.com/my-custom-resource"
+ Apart from above values - keys that are unprefixed or have kubernetes.io prefix are considered reserved and hence may not be used.
+
+ Capacity reported here 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.
+
+ A controller that receives PVC update with previously unknown resourceName should ignore the update for the purpose it was designed. For example - a controller that only is responsible for resizing capacity of the volume, should ignore PVC updates that change other valid resources associated with PVC.
+
+ This is an alpha field and requires enabling RecoverVolumeExpansionFailure feature.
- **capacity** (map[string]}}">Quantity)
@@ -212,10 +255,6 @@ PersistentVolumeClaimStatus is the current status of a persistent volume claim.
phase represents the current phase of PersistentVolumeClaim.
-- **resizeStatus** (string)
-
- 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.
-
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 3c30088340..552b4ba2d3 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
@@ -852,6 +852,13 @@ PersistentVolumeStatus is the current status of a persistent volume.
+- **lastPhaseTransitionTime** (Time)
+
+ lastPhaseTransitionTime is the time the phase transitioned from one to another and automatically resets to current time everytime a volume phase transitions. This is an alpha field and requires enabling PersistentVolumeLastPhaseTransitionTime feature.
+
+
+ *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.*
+
- **message** (string)
message is a human-readable message indicating details about why the volume is in this state.
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 a40e0f70f0..c36f69f035 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
@@ -529,6 +529,10 @@ JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-sc
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.
+ - **x-kubernetes-validations.fieldPath** (string)
+
+ fieldPath represents the field path returned when the validation fails. It must be a relative JSON path (i.e. with array notation) scoped to the location of this x-kubernetes-validations extension in the schema and refer to an existing field. e.g. when validation checks if a specific attribute `foo` under a map `testMap`, the fieldPath could be set to `.testMap.foo` If the validation checks two lists must have unique attributes, the fieldPath could be set to either of the list: e.g. `.testList` It does not support list numeric index. It supports child operation to refer to an existing field currently. Refer to [JSONPath support in Kubernetes](https://kubernetes.io/docs/reference/kubectl/jsonpath/) for more info. Numeric index of array is not supported. For field name which contains special characters, use `['specialName']` to refer the field name. e.g. for attribute `foo.34$` appears in a list `testList`, the fieldPath could be set to `.testList['foo.34$']`
+
- **x-kubernetes-validations.message** (string)
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"
@@ -537,6 +541,10 @@ JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-sc
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)+")"
+ - **x-kubernetes-validations.reason** (string)
+
+ reason provides a machine-readable validation failure reason that is returned to the caller when a request fails this validation rule. The HTTP status code returned to the caller will match the reason of the reason of the first failed validation rule. The currently supported reasons are: "FieldValueInvalid", "FieldValueForbidden", "FieldValueRequired", "FieldValueDuplicate". If not set, default to use "FieldValueInvalid". All future added reasons must be accepted by clients when reading this value and unknown reasons should be treated as FieldValueInvalid.
+
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 41cc4de342..6240ce40e6 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
@@ -132,7 +132,7 @@ MutatingWebhookConfiguration describes the configuration of and admission webhoo
- 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.
+ This is a beta feature and managed by the AdmissionWebhookMatchConditions feature gate.
*MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.*
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-v1beta1.md
similarity index 87%
rename from content/en/docs/reference/kubernetes-api/extend-resources/validating-admission-policy-v1alpha1.md
rename to content/en/docs/reference/kubernetes-api/extend-resources/validating-admission-policy-v1beta1.md
index a6d3d72d3e..1f9b8ef4bb 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-v1beta1.md
@@ -1,11 +1,11 @@
---
api_metadata:
- apiVersion: "admissionregistration.k8s.io/v1alpha1"
- import: "k8s.io/api/admissionregistration/v1alpha1"
+ apiVersion: "admissionregistration.k8s.io/v1beta1"
+ import: "k8s.io/api/admissionregistration/v1beta1"
kind: "ValidatingAdmissionPolicy"
content_type: "api_reference"
description: "ValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it."
-title: "ValidatingAdmissionPolicy v1alpha1"
+title: "ValidatingAdmissionPolicy v1beta1"
weight: 4
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: admissionregistration.k8s.io/v1alpha1`
+`apiVersion: admissionregistration.k8s.io/v1beta1`
-`import "k8s.io/api/admissionregistration/v1alpha1"`
+`import "k8s.io/api/admissionregistration/v1beta1"`
## ValidatingAdmissionPolicy {#ValidatingAdmissionPolicy}
@@ -32,7 +32,7 @@ ValidatingAdmissionPolicy describes the definition of an admission validation po
-- **apiVersion**: admissionregistration.k8s.io/v1alpha1
+- **apiVersion**: admissionregistration.k8s.io/v1beta1
- **kind**: ValidatingAdmissionPolicy
@@ -106,7 +106,7 @@ ValidatingAdmissionPolicy describes the definition of an admission validation po
- If failurePolicy=Ignore, the policy is skipped
- **
+ *MatchCondition represents a condition which must be fulfilled for a request to be sent to a webhook.*
- **spec.matchConditions.expression** (string), required
@@ -307,7 +307,9 @@ ValidatingAdmissionPolicy describes the definition of an admission validation po
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.
+ - '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. - 'namespaceObject' - The namespace object that the incoming object belongs to. The value is null for cluster-scoped resources. - 'variables' - Map of composited variables, from its name to its lazily evaluated value.
+ For example, a variable named 'foo' can be accessed as 'variables.foo'.
+ - '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.
@@ -342,12 +344,33 @@ ValidatingAdmissionPolicy describes the definition of an admission validation po
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.variables** ([]Variable)
+
+ *Patch strategy: merge on key `name`*
+
+ *Map: unique values on key name will be kept during a merge*
+
+ Variables contain definitions of variables that can be used in composition of other expressions. Each variable is defined as a named CEL expression. The variables defined here will be available under `variables` in other expressions of the policy except MatchConditions because MatchConditions are evaluated before the rest of the policy.
+
+ The expression of a variable can refer to other variables defined earlier in the list but not those after. Thus, Variables must be sorted by the order of first appearance and acyclic.
+
+
+ *Variable is the definition of a variable that is used for composition. A variable is defined as a named expression.*
+
+ - **spec.variables.expression** (string), required
+
+ Expression is the expression that will be evaluated as the value of the variable. The CEL expression has access to the same identifiers as the CEL expressions in Validation.
+
+ - **spec.variables.name** (string), required
+
+ Name is the name of the variable. The name must be a valid CEL identifier and unique among all variables. The variable can be accessed in other expressions through `variables` For example, if name is "foo", the variable will be available as `variables.foo`
+
- **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.
- *ValidatingAdmissionPolicyStatus represents the status of a ValidatingAdmissionPolicy.*
+ *ValidatingAdmissionPolicyStatus represents the status of an admission validation policy.*
- **status.conditions** ([]Condition)
@@ -427,7 +450,7 @@ ValidatingAdmissionPolicyList is a list of ValidatingAdmissionPolicy.
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
-- **items** ([]}}">ValidatingAdmissionPolicy)
+- **items** ([]}}">ValidatingAdmissionPolicy)
List of ValidatingAdmissionPolicy.
@@ -447,6 +470,10 @@ ValidatingAdmissionPolicyList is a list of ValidatingAdmissionPolicy.
ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters.
+For a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding.
+
+The CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.
+
- **apiVersion** (string)
@@ -623,18 +650,44 @@ ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with parame
- **spec.paramRef** (ParamRef)
- 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.
+ 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. If the policy does not specify a ParamKind then this field is ignored, and the rules are evaluated without a param.
- *ParamRef references a parameter resource*
+ *ParamRef describes how to locate the params to be used as input to expressions of rules applied by a policy binding.*
- **spec.paramRef.name** (string)
- Name of the resource being referenced.
+ name is the name of the resource being referenced.
+
+ One of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.
+
+ A single parameter used for all admission requests can be configured by setting the `name` field, leaving `selector` blank, and setting namespace if `paramKind` is namespace-scoped.
- **spec.paramRef.namespace** (string)
- Namespace of the referenced resource. Should be empty for the cluster-scoped resources
+ namespace is the namespace of the referenced resource. Allows limiting the search for params to a specific namespace. Applies to both `name` and `selector` fields.
+
+ A per-namespace parameter may be used by specifying a namespace-scoped `paramKind` in the policy and leaving this field empty.
+
+ - If `paramKind` is cluster-scoped, this field MUST be unset. Setting this field results in a configuration error.
+
+ - If `paramKind` is namespace-scoped, the namespace of the object being evaluated for admission will be used when this field is left unset. Take care that if this is left empty the binding must not match any cluster-scoped resources, which will result in an error.
+
+ - **spec.paramRef.parameterNotFoundAction** (string)
+
+ `parameterNotFoundAction` controls the behavior of the binding when the resource exists, and name or selector is valid, but there are no parameters matched by the binding. If the value is set to `Allow`, then no matched parameters will be treated as successful validation by the binding. If set to `Deny`, then no matched parameters will be subject to the `failurePolicy` of the policy.
+
+ Allowed values are `Allow` or `Deny`
+
+ Required
+
+ - **spec.paramRef.selector** (}}">LabelSelector)
+
+ selector can be used to match multiple param objects based on their labels. Supply selector: {} to match all resources of the ParamKind.
+
+ If multiple params are found, they are all evaluated with the policy expressions and the results are ANDed together.
+
+ One of `name` or `selector` must be set, but `name` and `selector` are mutually exclusive properties. If one is set, the other must be unset.
- **spec.policyName** (string)
@@ -683,7 +736,7 @@ ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with parame
#### HTTP Request
-GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}
+GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}
#### Parameters
@@ -702,7 +755,7 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### Response
-200 (}}">ValidatingAdmissionPolicy): OK
+200 (}}">ValidatingAdmissionPolicy): OK
401: Unauthorized
@@ -711,7 +764,7 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### HTTP Request
-GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}/status
+GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}/status
#### Parameters
@@ -730,7 +783,7 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### Response
-200 (}}">ValidatingAdmissionPolicy): OK
+200 (}}">ValidatingAdmissionPolicy): OK
401: Unauthorized
@@ -739,7 +792,7 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### HTTP Request
-GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
+GET /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies
#### Parameters
@@ -803,7 +856,7 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
#### Response
-200 (}}">ValidatingAdmissionPolicyList): OK
+200 (}}">ValidatingAdmissionPolicyList): OK
401: Unauthorized
@@ -812,12 +865,12 @@ GET /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
#### HTTP Request
-POST /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
+POST /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies
#### Parameters
-- **body**: }}">ValidatingAdmissionPolicy, required
+- **body**: }}">ValidatingAdmissionPolicy, required
@@ -846,11 +899,11 @@ POST /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
#### Response
-200 (}}">ValidatingAdmissionPolicy): OK
+200 (}}">ValidatingAdmissionPolicy): OK
-201 (}}">ValidatingAdmissionPolicy): Created
+201 (}}">ValidatingAdmissionPolicy): Created
-202 (}}">ValidatingAdmissionPolicy): Accepted
+202 (}}">ValidatingAdmissionPolicy): Accepted
401: Unauthorized
@@ -859,7 +912,7 @@ POST /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
#### HTTP Request
-PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}
+PUT /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}
#### Parameters
@@ -869,7 +922,7 @@ PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
name of the ValidatingAdmissionPolicy
-- **body**: }}">ValidatingAdmissionPolicy, required
+- **body**: }}">ValidatingAdmissionPolicy, required
@@ -898,9 +951,9 @@ PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### Response
-200 (}}">ValidatingAdmissionPolicy): OK
+200 (}}">ValidatingAdmissionPolicy): OK
-201 (}}">ValidatingAdmissionPolicy): Created
+201 (}}">ValidatingAdmissionPolicy): Created
401: Unauthorized
@@ -909,7 +962,7 @@ PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### HTTP Request
-PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}/status
+PUT /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}/status
#### Parameters
@@ -919,7 +972,7 @@ PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
name of the ValidatingAdmissionPolicy
-- **body**: }}">ValidatingAdmissionPolicy, required
+- **body**: }}">ValidatingAdmissionPolicy, required
@@ -948,9 +1001,9 @@ PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### Response
-200 (}}">ValidatingAdmissionPolicy): OK
+200 (}}">ValidatingAdmissionPolicy): OK
-201 (}}">ValidatingAdmissionPolicy): Created
+201 (}}">ValidatingAdmissionPolicy): Created
401: Unauthorized
@@ -959,7 +1012,7 @@ PUT /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{nam
#### HTTP Request
-PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}
+PATCH /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}
#### Parameters
@@ -1003,9 +1056,9 @@ PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{n
#### Response
-200 (}}">ValidatingAdmissionPolicy): OK
+200 (}}">ValidatingAdmissionPolicy): OK
-201 (}}">ValidatingAdmissionPolicy): Created
+201 (}}">ValidatingAdmissionPolicy): Created
401: Unauthorized
@@ -1014,7 +1067,7 @@ PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{n
#### HTTP Request
-PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}/status
+PATCH /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}/status
#### Parameters
@@ -1058,9 +1111,9 @@ PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{n
#### Response
-200 (}}">ValidatingAdmissionPolicy): OK
+200 (}}">ValidatingAdmissionPolicy): OK
-201 (}}">ValidatingAdmissionPolicy): Created
+201 (}}">ValidatingAdmissionPolicy): Created
401: Unauthorized
@@ -1069,7 +1122,7 @@ PATCH /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{n
#### HTTP Request
-DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{name}
+DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies/{name}
#### Parameters
@@ -1119,7 +1172,7 @@ DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies/{
#### HTTP Request
-DELETE /apis/admissionregistration.k8s.io/v1alpha1/validatingadmissionpolicies
+DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingadmissionpolicies
#### Parameters
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 6821958013..dbecb6fea7 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
@@ -132,7 +132,7 @@ ValidatingWebhookConfiguration describes the configuration of and admission webh
- 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.
+ This is a beta feature and managed by the AdmissionWebhookMatchConditions feature gate.
*MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.*
diff --git a/content/en/docs/reference/kubernetes-api/other-resources/validating-admission-policy-binding-list-v1alpha1.md b/content/en/docs/reference/kubernetes-api/other-resources/validating-admission-policy-binding-list-v1beta1.md
similarity index 73%
rename from content/en/docs/reference/kubernetes-api/other-resources/validating-admission-policy-binding-list-v1alpha1.md
rename to content/en/docs/reference/kubernetes-api/other-resources/validating-admission-policy-binding-list-v1beta1.md
index 2f1f75f560..58edc3226a 100644
--- a/content/en/docs/reference/kubernetes-api/other-resources/validating-admission-policy-binding-list-v1alpha1.md
+++ b/content/en/docs/reference/kubernetes-api/other-resources/validating-admission-policy-binding-list-v1beta1.md
@@ -1,11 +1,11 @@
---
api_metadata:
- apiVersion: "admissionregistration.k8s.io/v1alpha1"
- import: "k8s.io/api/admissionregistration/v1alpha1"
+ apiVersion: "admissionregistration.k8s.io/v1beta1"
+ import: "k8s.io/api/admissionregistration/v1beta1"
kind: "ValidatingAdmissionPolicyBindingList"
content_type: "api_reference"
description: ""
-title: "ValidatingAdmissionPolicyBindingList v1alpha1"
+title: "ValidatingAdmissionPolicyBindingList v1beta1"
weight: 1
auto_generated: true
---
@@ -21,8 +21,8 @@ guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
-`apiVersion: admissionregistration.k8s.io/v1alpha1`
+`apiVersion: admissionregistration.k8s.io/v1beta1`
-`import "k8s.io/api/admissionregistration/v1alpha1"`
+`import "k8s.io/api/admissionregistration/v1beta1"`
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 01345b6258..d182afa481 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
@@ -46,10 +46,6 @@ NetworkPolicy describes what network traffic is allowed for a set of Pods
spec represents the specification of the desired behavior for this NetworkPolicy.
-- **status** (}}">NetworkPolicyStatus)
-
- 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
-
@@ -198,54 +194,6 @@ NetworkPolicySpec provides the specification of a NetworkPolicy
-## NetworkPolicyStatus {#NetworkPolicyStatus}
-
-NetworkPolicyStatus describes the current state of the NetworkPolicy.
-
-
-
-- **conditions** ([]Condition)
-
- *Patch strategy: merge on key `type`*
-
- *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
-
-
- *Condition contains details for one aspect of the current state of this API Resource.*
-
- - **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.
-
-
- *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.*
-
- - **conditions.message** (string), required
-
- message is a human readable message indicating details about the transition. This may be an empty string.
-
- - **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.
-
- - **conditions.status** (string), required
-
- status of the condition, one of True, False, Unknown.
-
- - **conditions.type** (string), required
-
- type of condition in CamelCase or in foo.example.com/CamelCase.
-
- - **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.
-
-
-
-
-
## NetworkPolicyList {#NetworkPolicyList}
NetworkPolicyList is a list of NetworkPolicy objects.
@@ -306,39 +254,6 @@ GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}
-#### Response
-
-
-200 (}}">NetworkPolicy): OK
-
-401: Unauthorized
-
-
-### `get` read status of the specified NetworkPolicy
-
-#### HTTP Request
-
-GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}/status
-
-#### Parameters
-
-
-- **name** (*in path*): string, required
-
- name of the NetworkPolicy
-
-
-- **namespace** (*in path*): string, required
-
- }}">namespace
-
-
-- **pretty** (*in query*): string
-
- }}">pretty
-
-
-
#### Response
@@ -574,61 +489,6 @@ PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}
-- **dryRun** (*in query*): string
-
- }}">dryRun
-
-
-- **fieldManager** (*in query*): string
-
- }}">fieldManager
-
-
-- **fieldValidation** (*in query*): string
-
- }}">fieldValidation
-
-
-- **pretty** (*in query*): string
-
- }}">pretty
-
-
-
-#### Response
-
-
-200 (}}">NetworkPolicy): OK
-
-201 (}}">NetworkPolicy): Created
-
-401: Unauthorized
-
-
-### `update` replace status of the specified NetworkPolicy
-
-#### HTTP Request
-
-PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}/status
-
-#### Parameters
-
-
-- **name** (*in path*): string, required
-
- name of the NetworkPolicy
-
-
-- **namespace** (*in path*): string, required
-
- }}">namespace
-
-
-- **body**: }}">NetworkPolicy, required
-
-
-
-
- **dryRun** (*in query*): string
}}">dryRun
@@ -684,66 +544,6 @@ PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}
-- **dryRun** (*in query*): string
-
- }}">dryRun
-
-
-- **fieldManager** (*in query*): string
-
- }}">fieldManager
-
-
-- **fieldValidation** (*in query*): string
-
- }}">fieldValidation
-
-
-- **force** (*in query*): boolean
-
- }}">force
-
-
-- **pretty** (*in query*): string
-
- }}">pretty
-
-
-
-#### Response
-
-
-200 (}}">NetworkPolicy): OK
-
-201 (}}">NetworkPolicy): Created
-
-401: Unauthorized
-
-
-### `patch` partially update status of the specified NetworkPolicy
-
-#### HTTP Request
-
-PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}/status
-
-#### Parameters
-
-
-- **name** (*in path*): string, required
-
- name of the NetworkPolicy
-
-
-- **namespace** (*in path*): string, required
-
- }}">namespace
-
-
-- **body**: }}">Patch, required
-
-
-
-
- **dryRun** (*in query*): string
}}">dryRun
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 06b8f03269..92a773bcec 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
@@ -149,6 +149,8 @@ EndpointSlice represents a subset of the endpoints that implement a service. For
* Kubernetes-defined prefixed names:
* 'kubernetes.io/h2c' - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540
+ * 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
+ * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455
* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.
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 403dc9d535..ec8d225037 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
@@ -144,6 +144,8 @@ Endpoints is a collection of endpoints that implement the actual service. Exampl
* Kubernetes-defined prefixed names:
* 'kubernetes.io/h2c' - HTTP/2 over cleartext as described in https://www.rfc-editor.org/rfc/rfc7540
+ * 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
+ * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455
* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.
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 8159685fc4..ad18df1a1a 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
@@ -100,7 +100,16 @@ ServiceSpec describes the attributes that a user creates on a service.
- **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
+ * 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
+ * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455
+
+ * Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.
- **type** (string)
@@ -140,7 +149,7 @@ ServiceSpec describes the attributes that a user creates on a service.
- **loadBalancerIP** (string)
- 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.
+ 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. Using it is non-portable and it may not support dual-stack. Users are encouraged to use implementation-specific annotations when available.
- **loadBalancerSourceRanges** ([]string)
@@ -262,6 +271,10 @@ ServiceStatus represents the current status of a service.
IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers)
+ - **loadBalancer.ingress.ipMode** (string)
+
+ IPMode specifies how the load-balancer IP behaves, and may only be specified when the ip field is specified. Setting this to "VIP" indicates that traffic is delivered to the node with the destination set to the load-balancer's IP and port. Setting this to "Proxy" indicates that traffic is delivered to the node or pod with the destination set to the node's IP and node port or the pod's IP and port. Service implementations may use this information to adjust traffic routing.
+
- **loadBalancer.ingress.ports** ([]PortStatus)
*Atomic: will be replaced during a merge*
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 00790c4af0..0afe9886ee 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
@@ -117,14 +117,14 @@ JobSpec describes how the job execution will look like.
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
-### Alpha level
+### Beta level
- **podFailurePolicy** (PodFailurePolicy)
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.
- This field is alpha-level. To use this field, you must enable the `JobPodFailurePolicy` feature gate (disabled by default).
+ This field is beta-level. It can be used when the `JobPodFailurePolicy` feature gate is enabled (enabled by default).
*PodFailurePolicy describes how failed pods influence the backoffLimit.*
@@ -144,6 +144,10 @@ JobSpec describes how the job execution will look like.
- FailJob: indicates that the pod's job is marked as Failed and all
running pods are terminated.
+ - FailIndex: indicates that the pod's index is marked as Failed and will
+ not be restarted.
+ This value is alpha-level. It can be used when the
+ `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).
- 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
@@ -196,6 +200,26 @@ JobSpec describes how the job execution will look like.
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.
+### Alpha level
+
+
+- **backoffLimitPerIndex** (int32)
+
+ Specifies the limit for the number of retries within an index before marking this index as failed. When enabled the number of failures per index is kept in the pod's batch.kubernetes.io/job-index-failure-count annotation. It can only be set when Job's completionMode=Indexed, and the Pod's restart policy is Never. The field is immutable. This field is alpha-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).
+
+- **maxFailedIndexes** (int32)
+
+ Specifies the maximal number of failed indexes before marking the Job as failed, when backoffLimitPerIndex is set. Once the number of failed indexes exceeds this number the entire Job is marked as Failed and its execution is terminated. When left as null the job continues execution of all of its indexes and is marked with the `Complete` Job condition. It can only be specified when backoffLimitPerIndex is set. It can be null or up to completions. It is required and must be less than or equal to 10^4 when is completions greater than 10^5. This field is alpha-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).
+
+- **podReplacementPolicy** (string)
+
+ podReplacementPolicy specifies when to create replacement Pods. Possible values are: - TerminatingOrFailed means that we recreate pods
+ when they are terminating (has a metadata.deletionTimestamp) or failed.
+ - Failed means to wait until a previously created Pod is fully terminated (has phase
+ Failed or Succeeded) before creating a replacement Pod.
+
+ When using podFailurePolicy, Failed is the the only allowed value. TerminatingOrFailed and Failed are allowed values when podFailurePolicy is not in use. This is an alpha field. Enable JobPodReplacementPolicy to be able to use this field.
+
## JobStatus {#JobStatus}
@@ -312,6 +336,19 @@ JobStatus represents the current state of a Job.
This field is beta-level. The job controller populates the field when the feature gate JobReadyPods is enabled (enabled by default).
+### Alpha level
+
+
+- **failedIndexes** (string)
+
+ FailedIndexes holds the failed indexes when backoffLimitPerIndex=true. The indexes are represented in the text format analogous as for the `completedIndexes` field, ie. they are kept 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 failed indexes are 1, 3, 4, 5 and 7, they are represented as "1,3-5,7". This field is alpha-level. It can be used when the `JobBackoffLimitPerIndex` feature gate is enabled (disabled by default).
+
+- **terminating** (int32)
+
+ The number of pods which are terminating (in phase Pending or Running and have a deletionTimestamp).
+
+ This field is alpha-level. The job controller populates the field when the feature gate JobPodReplacementPolicy is enabled (disabled by default).
+
## JobList {#JobList}
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 16813f6973..7c6bdf614c 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
@@ -430,7 +430,7 @@ PodSpec is a description of a pod.
- **securityContext.seccompProfile.localhostProfile** (string)
- 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's configured seccomp profile location. Must only be set if type is "Localhost".
+ 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's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type.
- **securityContext.seLinuxOptions** (SELinuxOptions)
@@ -487,7 +487,7 @@ PodSpec is a description of a pod.
- **securityContext.windowsOptions.hostProcess** (boolean)
- HostProcess determines if a container should be run as a 'Host Process' 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'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.
+ HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod'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.
- **securityContext.windowsOptions.runAsUserName** (string)
@@ -536,9 +536,7 @@ PodSpec is a description of a pod.
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 \-\, where \ 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.
+ 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 pod name and resource name, along with a generated component, will be used to form a unique name for the ResourceClaim, which will be recorded in pod.status.resourceClaimStatuses.
This field is immutable and no changes will be made to the corresponding ResourceClaim by the control plane after creating the ResourceClaim.
@@ -903,6 +901,10 @@ A single application container that you want to run within a pod.
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'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
+- **restartPolicy** (string)
+
+ RestartPolicy defines the restart behavior of individual containers in a pod. This field may only be set for init containers, and the only allowed value is "Always". For non-init containers or when this field is not specified, the restart behavior is defined by the Pod's restart policy and the container type. Setting the RestartPolicy as "Always" for the init container will have the following effect: this init container will be continually restarted on exit until all regular containers have terminated. Once all regular containers have completed, all init containers with restartPolicy "Always" will be shut down. This lifecycle differs from normal init containers and is often referred to as a "sidecar" container. Although this init container still starts in the init container sequence, it does not wait for the container to complete before proceeding to the next init container. Instead, the next init container starts immediately after this init container is started, or after any startupProbe has successfully completed.
+
### Security Context
@@ -971,7 +973,7 @@ A single application container that you want to run within a pod.
- **securityContext.seccompProfile.localhostProfile** (string)
- 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's configured seccomp profile location. Must only be set if type is "Localhost".
+ 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's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type.
- **securityContext.seLinuxOptions** (SELinuxOptions)
@@ -1013,7 +1015,7 @@ A single application container that you want to run within a pod.
- **securityContext.windowsOptions.hostProcess** (boolean)
- HostProcess determines if a container should be run as a 'Host Process' 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'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.
+ HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod'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.
- **securityContext.windowsOptions.runAsUserName** (string)
@@ -1284,6 +1286,10 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
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.
+- **restartPolicy** (string)
+
+ Restart policy for the container to manage the restart behavior of each container within a pod. This may only be set for init containers. You cannot set this field on ephemeral containers.
+
### Debugging
@@ -1367,7 +1373,7 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
- **securityContext.seccompProfile.localhostProfile** (string)
- 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's configured seccomp profile location. Must only be set if type is "Localhost".
+ 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's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type.
- **securityContext.seLinuxOptions** (SELinuxOptions)
@@ -1409,7 +1415,7 @@ To add an ephemeral container, use the ephemeralcontainers subresource of an exi
- **securityContext.windowsOptions.hostProcess** (boolean)
- HostProcess determines if a container should be run as a 'Host Process' 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'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.
+ HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod'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.
- **securityContext.windowsOptions.runAsUserName** (string)
@@ -1554,7 +1560,7 @@ LifecycleHandler defines a specific action that should be taken in a lifecycle h
- **httpGet.httpHeaders.name** (string), required
- The header field name
+ The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header.
- **httpGet.httpHeaders.value** (string), required
@@ -1826,7 +1832,7 @@ Probe describes a health check to be performed against a container to determine
- **httpGet.httpHeaders.name** (string), required
- The header field name
+ The header field name. This will be canonicalized upon output, so case-variant names will be understood as the same header.
- **httpGet.httpHeaders.value** (string), required
@@ -1915,7 +1921,22 @@ PodStatus represents information about the status of a pod. Status may trail the
- **hostIP** (string)
- IP address of the host to which the pod is assigned. Empty if not yet scheduled.
+ hostIP holds the IP address of the host to which the pod is assigned. Empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns mean that HostIP will not be updated even if there is a node is assigned to pod
+
+- **hostIPs** ([]HostIP)
+
+ *Patch strategy: merge on key `ip`*
+
+ *Atomic: will be replaced during a merge*
+
+ hostIPs holds the IP addresses allocated to the host. If this field is specified, the first entry must match the hostIP field. This list is empty if the pod has not started yet. A pod can be assigned to a node that has a problem in kubelet which in turns means that HostIPs will not be updated even if there is a node is assigned to this pod.
+
+
+ *HostIP represents a single IP address allocated to the host.*
+
+ - **hostIPs.ip** (string)
+
+ IP is the IP address assigned to the host
- **startTime** (Time)
@@ -1942,7 +1963,7 @@ PodStatus represents information about the status of a pod. Status may trail the
- **podIP** (string)
- IP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.
+ podIP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.
- **podIPs** ([]PodIP)
@@ -1951,13 +1972,11 @@ PodStatus represents information about the status of a pod. Status may trail the
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.
- *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.*
+ *PodIP represents a single IP address allocated to the pod.*
- **podIPs.ip** (string)
- ip is an IP address (IPv4 or IPv6) assigned to the pod
+ IP is the IP address assigned to the pod
- **conditions** ([]PodCondition)
@@ -2023,6 +2042,25 @@ PodStatus represents information about the status of a pod. Status may trail the
*ContainerStatus contains details for the current status of this container.*
+- **resourceClaimStatuses** ([]PodResourceClaimStatus)
+
+ *Patch strategies: retainKeys, merge on key `name`*
+
+ *Map: unique values on key name will be kept during a merge*
+
+ Status of resource claims.
+
+
+ *PodResourceClaimStatus is stored in the PodStatus for each PodResourceClaim which references a ResourceClaimTemplate. It stores the generated name for the corresponding ResourceClaim.*
+
+ - **resourceClaimStatuses.name** (string), required
+
+ Name uniquely identifies this resource claim inside the pod. This must match the name of an entry in pod.spec.resourceClaims, which implies that the string must be a DNS_LABEL.
+
+ - **resourceClaimStatuses.resourceClaimName** (string)
+
+ ResourceClaimName is the name of the ResourceClaim that was generated for the Pod in the namespace of the Pod. It this is unset, then generating a ResourceClaim was not necessary. The pod.spec.resourceClaims entry can be ignored in this case.
+
- **resize** (string)
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"
From 08f4d4847687a2ef9894ffd4d30dd5ab70d6fdb1 Mon Sep 17 00:00:00 2001
From: Michal Wozniak
Date: Fri, 7 Jul 2023 09:41:30 +0200
Subject: [PATCH 095/446] Docs update for Alpha JobBackoffLimitPerIndex
---
.../concepts/workloads/controllers/job.md | 36 +++++++++++++++++++
.../feature-gates.md | 3 ++
.../job-backoff-limit-per-index-example.yaml | 24 +++++++++++++
3 files changed, 63 insertions(+)
create mode 100644 content/en/examples/controllers/job-backoff-limit-per-index-example.yaml
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index be6a66c9db..b7e4c10c3f 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -318,6 +318,9 @@ caused by previous runs.
By default, each pod failure is counted towards the `.spec.backoffLimit` limit,
see [pod backoff failure policy](#pod-backoff-failure-policy). However, you can
customize handling of pod failures by setting the Job's [pod failure policy](#pod-failure-policy).
+Additionally, you can choose to count the pod failures independently for each
+index of an Indexed Job by setting the `.spec.backoffLimitPerIndex` field
+(see [backoff limit per index](#backoff-limit-per-index)).
Note that even if you specify `.spec.parallelism = 1` and `.spec.completions = 1` and
`.spec.template.spec.restartPolicy = "Never"`, the same program may
@@ -363,6 +366,39 @@ will be terminated once the job backoff limit has been reached. This can make de
from failed Jobs is not lost inadvertently.
{{< /note >}}
+### Backoff limit per index {#backoff-limit-per-index}
+
+{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
+
+{{< note >}}
+You can only configure the backoff limit per index for a Job, if you
+have the `JobBackoffLimitPerIndex` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+enabled in your cluster. This feature is only available for Indexed Jobs, which
+use the `restartPolicy: Never`.
+{{< /note >}}
+
+When you run an Indexed Job, you may want to handle pod failures for different
+indexes as counted independently. To do so, set the `.spec.backoffLimitPerIndex`
+to specify the the maximal number of pod failures per index. When the number is
+exceeded for an index, the index is marked as failed in the
+`.status.failedIndexes` field. Note that, a failing index does not interrupt
+execution of other indexes. You can additionally limit the maximal number of
+indexes marked failed by setting the `.spec.maxFailedIndexes` field. In that case,
+the the number of failed indexes is exceeded, then the entire Job is marked
+failed and execution all pods and indexed is terminated.
+
+When all indexes finishes for a Job using this feature, and there is at least
+one failed index, then the entire Job is marked as failed, even if some indexes
+are finished successfully.
+
+Here is a manifest for an Indexed Job that defines a `backoffLimitPerIndex`:
+
+{{< codenew file="/controllers/job-backoff-limit-per-index-example.yaml" >}}
+
+In the example above, the Job controller will allow for one restart for each
+of the indexes. When the total number of failed indexes exceeds 5, then
+the entire Job is terminated.
+
### Pod failure policy {#pod-failure-policy}
{{< feature-state for_k8s_version="v1.26" state="beta" >}}
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 d892d3f5be..04c1f891bb 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
@@ -118,6 +118,7 @@ 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 | |
+| `JobBackoffLimitPerIndex` | `false` | Alpha | 1.28 | 1.28 |
| `JobPodFailurePolicy` | `false` | Alpha | 1.25 | 1.25 |
| `JobPodFailurePolicy` | `true` | Beta | 1.26 | |
| `JobReadyPods` | `false` | Alpha | 1.23 | 1.23 |
@@ -551,6 +552,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
and volume controllers.
- `JobMutableNodeSchedulingDirectives`: Allows updating node scheduling directives in
the pod template of [Job](/docs/concepts/workloads/controllers/job).
+- `JobBackoffLimitPerIndex`: Allows users to specify the maximal number of pod
+ retries per index in Indexed jobs.
- `JobPodFailurePolicy`: Allow users to specify handling of pod failures based on container
exit codes and pod conditions.
- `JobReadyPods`: Enables tracking the number of Pods that have a `Ready`
diff --git a/content/en/examples/controllers/job-backoff-limit-per-index-example.yaml b/content/en/examples/controllers/job-backoff-limit-per-index-example.yaml
new file mode 100644
index 0000000000..5b229458d5
--- /dev/null
+++ b/content/en/examples/controllers/job-backoff-limit-per-index-example.yaml
@@ -0,0 +1,24 @@
+apiVersion: batch/v1
+kind: Job
+metadata:
+ name: job-backoff-limit-per-index-example
+spec:
+ completions: 10
+ parallelism: 3
+ completionMode: Indexed # required for the feature
+ backoffLimitPerIndex: 1 # maximal number of failures per index
+ maxFailedIndexes: 5 # maximal number of failed indexes before terminating the Job execution
+ template:
+ spec:
+ restartPolicy: Never # required for the feature
+ containers:
+ - name: example
+ image: python
+ command:
+ - python3
+ - -c
+ - |
+ import os, sys
+ print("Hello world")
+ if int(os.environ.get("JOB_COMPLETION_INDEX")) % 2 == 0:
+ sys.exit(1)
From db4ba0632d48a37082d5396541635cfa15baee0a Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Thu, 27 Jul 2023 10:24:42 -0400
Subject: [PATCH 096/446] add feature toggle for podreplacementpolicy
---
.../reference/command-line-tools-reference/feature-gates.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 9d59376647..a2ced7aca1 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -120,6 +120,7 @@ For a reference to old feature gates that are removed, please refer to
| `InTreePluginvSphereUnregister` | `false` | Alpha | 1.21 | |
| `JobPodFailurePolicy` | `false` | Alpha | 1.25 | 1.25 |
| `JobPodFailurePolicy` | `true` | Beta | 1.26 | |
+| `JobPodReplacementPolicy` | `false` | Alpha | 1.28 | |
| `JobReadyPods` | `false` | Alpha | 1.23 | 1.23 |
| `JobReadyPods` | `true` | Beta | 1.24 | |
| `KMSv2` | `false` | Alpha | 1.25 | 1.26 |
@@ -551,6 +552,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
the pod template of [Job](/docs/concepts/workloads/controllers/job).
- `JobPodFailurePolicy`: Allow users to specify handling of pod failures based on container
exit codes and pod conditions.
+- `JobPodReplacementPolicy`: Allows users to specify pod replacement for terminating pods in a [Job](/docs/concepts/workloads/controllers/job)
- `JobReadyPods`: Enables tracking the number of Pods that have a `Ready`
[condition](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions).
The count of `Ready` pods is recorded in the
From cd0de2832aa65ee974eed8ff4eb6af2c1f815bf9 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Thu, 27 Jul 2023 10:34:26 -0400
Subject: [PATCH 097/446] address comments
---
content/en/docs/concepts/workloads/controllers/job.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index fd6572ba75..2075380420 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -878,7 +878,7 @@ scaling an indexed Job, such as MPI, Horovord, Ray, and PyTorch training jobs.
{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
{{< note >}}
-You can only enable `PodReplacementPolicy` for Jobs if you set `JobPodReplacementPolicy`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to true.
+You can only set `podReplacementPolicy` on Jobs if you enable the `JobPodReplacementPolicy` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
{{< /note >}}
By default, the Job controller recreates pods as soon they are either failed or terminating (have a deletion timestamp).
@@ -886,7 +886,7 @@ This means that, at a given time, the number of running Pods for the Jobs can be
You may choose to create replacement pods only when the terminating pod is fully terminal (has `status.phase: Failed`). To do this, set the `.spec.podReplacementPolicy: Failed`.
This will only recreate pods once they are terminated.
-Default behavior will be to recreate upon deletion (`DeletionTimestamp != nil`).
+The default policy is `FailedOrTerminating`, meaning that the control plane creates replacement Pods upon deletion (`DeletionTimestamp != nil`).
```yaml
kind: Job
@@ -913,7 +913,7 @@ status:
terminating: 1 # if pod is terminating
```
-When [PodFailurePolicy](#pod-failure-policy) is enabled, a Job will have a default (and only this value is allowed) value of `Failed`.
+When you use a [podFailurePolicy](#pod-failure-policy) in a Job, the Job will have a default `podReplacementPolicy` value of `Failed`, and this is the only policy allowed.
If `JobPodReplacementPolicy` is disabled and `podFailurePolicy` is enabled, a Job will wait for terminating pods to be fully terminated before marking the pod as failed.
In this case, you will not be able to inspect the `terminating` field.
From 19cc74259014aaf33873831f5c538d978e7d8401 Mon Sep 17 00:00:00 2001
From: Rishit Dagli
Date: Thu, 27 Jul 2023 15:15:47 +0000
Subject: [PATCH 098/446] add 1.28 to release schedule for 1.28 release
---
data/releases/schedule.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index 3907c904a1..80c10aa266 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -2,6 +2,12 @@
# This file helps to populate the /releases page, and is also parsed to find out the
# latest patch version for a minor release.
schedules:
+- release: 1.28
+ releaseDate: 2023-08-15
+ next: 1.28.1
+ cherryPickDeadline: 2023-09-08
+ targetDate: 2023-09-13
+ endOfLifeDate: 2024-10-28
- release: 1.27
releaseDate: 2024-04-11
maintenanceModeStartDate: 2024-04-28
From e31ceb6cb173681eee2f0293aeebc30ddfb0aee2 Mon Sep 17 00:00:00 2001
From: Daniel Vega-Myhre
Date: Thu, 27 Jul 2023 18:26:08 +0000
Subject: [PATCH 099/446] add feature gate docs
---
.../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 88e2cae5d5..a7157401dc 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
@@ -651,6 +651,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `PodAndContainerStatsFromCRI`: Configure the kubelet to gather container and pod stats from the CRI container runtime rather than gathering them from cAdvisor.
As of 1.26, this also includes gathering metrics from CRI and emitting them over `/metrics/cadvisor` (rather than having cAdvisor emit them directly).
- `PodDisruptionConditions`: Enables support for appending a dedicated pod condition indicating that the pod is being deleted due to a disruption.
+- `PodIndexLabel`: Enables the Job controller and StatefulSet controller to add the pod index as a label when creating new pods. See [Job completion mode docs](/docs/concepts/workloads/controllers/job#completion-mode) and [StatefulSet pod index label docs](/docs/concepts/workloads/controllers/statefulset/#pod-index-label) for more details.
- `PodReadyToStartContainersCondition`: Enable the kubelet to mark the [PodReadyToStartContainers](/docs/concepts/workloads/pods/pod-lifecycle/#pod-has-network)
condition on pods. This was previously (1.25-1.27) known as `PodHasNetworkCondition`.
- `PodSchedulingReadiness`: Enable setting `schedulingGates` field to control a Pod's [scheduling readiness](/docs/concepts/scheduling-eviction/pod-scheduling-readiness).
From f3fb1cbcfc53bae305134741cd569577f2ec28c9 Mon Sep 17 00:00:00 2001
From: Daniel Vega-Myhre
Date: Thu, 27 Jul 2023 18:31:50 +0000
Subject: [PATCH 100/446] mention feature gates in label docs
---
.../en/docs/reference/labels-annotations-taints/_index.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 6450607233..36e5d97a2f 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -238,7 +238,8 @@ When a StatefulSet controller creates a Pod for the StatefulSet, it sets this la
The value of the label is the ordinal index of the pod being created.
See [Pod Index Label](/docs/concepts/workloads/controllers/statefulset/#pod-index-label)
-in the StatefulSet topic for more details.
+in the StatefulSet topic for more details. Note the [PodIndexLabel](content/en/docs/reference/command-line-tools-reference/feature-gates.md) feature gate must be enabled
+for this label to be added to pods.
### cluster-autoscaler.kubernetes.io/safe-to-evict
@@ -1056,6 +1057,9 @@ Used on: Pod
The Job controller in the kube-controller-manager sets this as a label and annotation for Pods
created with Indexed [completion mode](/docs/concepts/workloads/controllers/job/#completion-mode).
+Note the [PodIndexLabel](content/en/docs/reference/command-line-tools-reference/feature-gates.md) feature gate must be enabled
+for this to be added as a pod **label**, otherwise it will just be an annotation.
+
### kubectl.kubernetes.io/default-container
Type: Annotation
From fe4c6b8a08bce5fc074a55a23834a25a51a1ecf2 Mon Sep 17 00:00:00 2001
From: Hemant Kumar
Date: Fri, 28 Jul 2023 13:14:59 -0400
Subject: [PATCH 101/446] Remove references to older alpha field
---
content/en/docs/concepts/storage/persistent-volumes.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index dfa08602f8..c22c6c1623 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -492,7 +492,7 @@ value you previously tried.
This is useful if expansion to a higher value did not succeed because of capacity constraint.
If that has happened, or you suspect that it might have, you can retry expansion by specifying a
size that is within the capacity limits of underlying storage provider. You can monitor status of
-resize operation by watching `.status.resizeStatus` and events on the PVC.
+resize operation by watching `.status.allocatedResourceStatuses` and events on the PVC.
Note that,
although you can specify a lower amount of storage than what was requested previously,
From 84ce0f12c602f861bc3b788ba75109276a081837 Mon Sep 17 00:00:00 2001
From: Mohammed Affan
Date: Mon, 24 Jul 2023 22:23:38 +0530
Subject: [PATCH 102/446] Fix storageclass pvc statement
---
content/en/docs/concepts/storage/persistent-volumes.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index feb9141412..f0843b31cb 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -847,9 +847,9 @@ is turned on.
PVs of that default. Specifying a default StorageClass is done by setting the
annotation `storageclass.kubernetes.io/is-default-class` equal to `true` in
a StorageClass object. If the administrator does not specify a default, the
- cluster responds to PVC creation as if the admission plugin were turned off. If
- more than one default is specified, the admission plugin forbids the creation of
- all PVCs.
+ cluster responds to PVC creation as if the admission plugin were turned off. If more than one
+ default StorageClass is specified, the newest default is used when the
+ PVC is dynamically provisioned.
* If the admission plugin is turned off, there is no notion of a default
StorageClass. All PVCs that have `storageClassName` set to `""` can be
bound only to PVs that have `storageClassName` also set to `""`.
From 4afba1c60990420016905a930ba9f7156c1b71a8 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Mon, 31 Jul 2023 14:15:34 -0400
Subject: [PATCH 103/446] add suggestions
---
.../concepts/workloads/controllers/job.md | 35 ++++++++++---------
.../feature-gates.md | 2 +-
2 files changed, 20 insertions(+), 17 deletions(-)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 2075380420..eb303741cd 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -458,9 +458,9 @@ ensures that deleted pods have their finalizers removed by the Job controller.
{{< /note >}}
{{< note >}}
-Since Kubernetes v1.28, when pod failure policy is used, the Job controller recreates
-terminating pods only once they reach the terminal `Failed` phase. This behavior is analogous
-to when using `podRecreationPolicy: Failed`, see [pod replacement policy](#pod-replacement-policy) for more details.
+Starting with Kubernetes v1.28, when Pod failure policy is used, the Job controller recreates
+terminating Pods only once these Pods reach the terminal `Failed` phase. This behavior is similar
+to `podRecreationPolicy: Failed`. For more information, see [Pod replacement policy](#pod-replacement-policy).
{{< /note >}}
## Job termination and cleanup
@@ -873,7 +873,7 @@ 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.
-### Pod Replacement Policy
+### Delayed creation of replacement pods
{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
@@ -881,12 +881,19 @@ scaling an indexed Job, such as MPI, Horovord, Ray, and PyTorch training jobs.
You can only set `podReplacementPolicy` on Jobs if you enable the `JobPodReplacementPolicy` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
{{< /note >}}
-By default, the Job controller recreates pods as soon they are either failed or terminating (have a deletion timestamp).
-This means that, at a given time, the number of running Pods for the Jobs can be greater than `parallelism` or, if using Indexed Jobs, more than one running Pod per index, if some of the Pods are terminating.
+By default, the Job controller recreates Pods as soon they either fail or are terminating (have a deletion timestamp).
+This means that, at a given time, when some of the Pods are terminating, the number of running Pods for the Jobs can be greater than `parallelism` or greater than one Pod per index (if using Indexed Jobs).
-You may choose to create replacement pods only when the terminating pod is fully terminal (has `status.phase: Failed`). To do this, set the `.spec.podReplacementPolicy: Failed`.
-This will only recreate pods once they are terminated.
-The default policy is `FailedOrTerminating`, meaning that the control plane creates replacement Pods upon deletion (`DeletionTimestamp != nil`).
+You may choose to create replacement Pods only when the terminating Pod is fully terminal (has `status.phase: Failed`). To do this, set the `.spec.podReplacementPolicy: Failed`.
+This will only recreate Pods once they are terminated.
+The default replacement policy depends on whether the Job has a `podFailurePolicy` set.
+With no Pod failure policy defined for a Job, omitting the `podReplacementPolicy` field selects the
+`FailedOrTerminating` replacement policy:
+the control plane creates replacement Pods immediately upon Pod deletion
+(as soon as the control plane sees that a Pod for this Job has `deletionTimestamp` set).
+For Jobs with a Pod failure policy set, the default `podReplacementPolicy` is `Failed`, and no other
+value is permitted.
+See [Pod failure policy](#pod-failure-policy) to learn more about Pod failure policies for Jobs.
```yaml
kind: Job
@@ -898,8 +905,8 @@ spec:
...
```
-You can inspect a new field in the JobStatus called `terminating`.
-This will report the number pods that are currently terminating and is easily viewable in the status.
+Provided your cluster has the feature gate enabled, you can inspect the `.status.terminating` field of a Job.
+The value of the field is the number of Pods owned by the Job that are currently terminating.
```shell
kubectl get jobs/myjob -o yaml
@@ -910,13 +917,9 @@ apiVersion: batch/v1
kind: Job
# .metadata and .spec omitted
status:
- terminating: 1 # if pod is terminating
+ terminating: 3 # three Pods are terminating and have not yet reached the Failed phase
```
-When you use a [podFailurePolicy](#pod-failure-policy) in a Job, the Job will have a default `podReplacementPolicy` value of `Failed`, and this is the only policy allowed.
-If `JobPodReplacementPolicy` is disabled and `podFailurePolicy` is enabled, a Job will wait for terminating pods to be fully terminated before marking the pod as failed.
-In this case, you will not be able to inspect the `terminating` field.
-
## 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 a2ced7aca1..cf720e4070 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
@@ -552,7 +552,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
the pod template of [Job](/docs/concepts/workloads/controllers/job).
- `JobPodFailurePolicy`: Allow users to specify handling of pod failures based on container
exit codes and pod conditions.
-- `JobPodReplacementPolicy`: Allows users to specify pod replacement for terminating pods in a [Job](/docs/concepts/workloads/controllers/job)
+- `JobPodReplacementPolicy`: Allows you to specify pod replacement for terminating pods in a [Job](/docs/concepts/workloads/controllers/job)
- `JobReadyPods`: Enables tracking the number of Pods that have a `Ready`
[condition](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions).
The count of `Ready` pods is recorded in the
From 6b0751c6790406f2e605bdb919ed5cfb349ed777 Mon Sep 17 00:00:00 2001
From: Max Cameron
Date: Tue, 1 Aug 2023 10:03:15 +0100
Subject: [PATCH 104/446] Update storage-classes.md
Using the documented allowed topologies config I get the following deprecation warning:
```
Warning: allowedTopologies[0].matchLabelExpressions[0].key: deprecated since v1.17; use "topology.kubernetes.io/zone" instead
```
Using "topology.kubernetes.io/zone", I get successful deployment:
```
kubectl edit storageclass/gp2
storageclass.storage.k8s.io/gp2 edited
```
---
content/en/docs/concepts/storage/storage-classes.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/storage/storage-classes.md b/content/en/docs/concepts/storage/storage-classes.md
index c1d686dfa1..93052b3ae9 100644
--- a/content/en/docs/concepts/storage/storage-classes.md
+++ b/content/en/docs/concepts/storage/storage-classes.md
@@ -243,7 +243,7 @@ parameters:
volumeBindingMode: WaitForFirstConsumer
allowedTopologies:
- matchLabelExpressions:
- - key: failure-domain.beta.kubernetes.io/zone
+ - key: topology.kubernetes.io/zone
values:
- us-central-1a
- us-central-1b
From fde22b5031245fb28d79a11a852c636f3286d90b Mon Sep 17 00:00:00 2001
From: Matthias Bertschy
Date: Thu, 29 Jun 2023 07:41:59 +0200
Subject: [PATCH 105/446] adding Sidecar Containers alpha feature
Signed-off-by: Matthias Bertschy
---
.../en/docs/concepts/workloads/pods/_index.md | 14 +++++-
.../workloads/pods/init-containers.md | 43 ++++++++++++++++++-
.../feature-gates.md | 8 +++-
.../application/deployment-sidecar.yaml | 34 +++++++++++++++
.../examples/application/job/job-sidecar.yaml | 26 +++++++++++
5 files changed, 121 insertions(+), 4 deletions(-)
create mode 100644 content/en/examples/application/deployment-sidecar.yaml
create mode 100644 content/en/examples/application/job/job-sidecar.yaml
diff --git a/content/en/docs/concepts/workloads/pods/_index.md b/content/en/docs/concepts/workloads/pods/_index.md
index e9fba178e2..19f2564c30 100644
--- a/content/en/docs/concepts/workloads/pods/_index.md
+++ b/content/en/docs/concepts/workloads/pods/_index.md
@@ -112,7 +112,17 @@ that updates those files from a remote source, as in the following diagram:
{{< figure src="/images/docs/pod.svg" alt="Pod creation diagram" class="diagram-medium" >}}
-Some Pods have {{< glossary_tooltip text="init containers" term_id="init-container" >}} as well as {{< glossary_tooltip text="app containers" term_id="app-container" >}}. Init containers run and complete before the app containers are started.
+Some Pods have {{< glossary_tooltip text="init containers" term_id="init-container" >}}
+as well as {{< glossary_tooltip text="app containers" term_id="app-container" >}}.
+By default, init containers run and complete before the app containers are started.
+
+{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
+
+Enabling the [SidecarContainers feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+allows specifying a restartPolicy=Always to init containers, making sure they are
+kept running during the entire lifetime of the Pod.
+See [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/init-containers/#sidecar-containers-and-restartpolicy)
+for more details.
Pods natively provide two kinds of shared resources for their constituent containers:
[networking](#pod-networking) and [storage](#pod-storage).
@@ -366,4 +376,4 @@ To understand the context for why Kubernetes wraps a common Pod API in other res
* [Borg](https://research.google.com/pubs/pub43438.html)
* [Marathon](https://mesosphere.github.io/marathon/docs/rest-api.html)
* [Omega](https://research.google/pubs/pub41684/)
-* [Tupperware](https://engineering.fb.com/data-center-engineering/tupperware/).
+* [Tupperware](https://engineering.fb.com/data-center-engineering/tupperware/).
\ No newline at end of file
diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md
index c7e0707e88..e0e5f26fce 100644
--- a/content/en/docs/concepts/workloads/pods/init-containers.md
+++ b/content/en/docs/concepts/workloads/pods/init-containers.md
@@ -289,7 +289,47 @@ The Pod which is already running correctly would be killed by `activeDeadlineSec
The name of each app and init container in a Pod must be unique; a
validation error is thrown for any container sharing a name with another.
-### Resources
+#### API for sidecar containers
+
+{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
+
+Starting with Kubernetes 1.28 in alpha, a feature gate named `SidecarContainers`
+allows to specify a `restartPolicy` for init containers which is independent of
+the Pod and other init containers. Container [probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe)
+can also be added to control their lifecycle.
+
+If an init container is created with its `restartPolicy` set to `Always`, it will
+start and remain running during the entire life of the Pod, which is useful for
+running supporting services separated from the main application containers.
+
+If a `readinessProbe` is specified for this init container, its result will be used
+to determine the `ready` state of the Pod.
+
+Since these containers are defined as init containers, they benefit from the same
+ordering and sequential guarantees as other init containers, allowing them to
+be mixed with other init containers into complex Pod initialization flows.
+
+The only difference is that they are not required to complete before the next
+init container starts, so a next init container will start after the current
+container status has been set to `Pod.status.containerStatuses[id of container].started=true`
+as a result of its `startupProbe` succeeding.
+
+This feature can be used to implement the sidecar container pattern in a more
+robust way, as the kubelet always restarts a sidecar container if it fails.
+
+Here's an example of a Deployment with two containers, one of which is a sidecar:
+
+{{% codenew language="yaml" file="application/deployment-sidecar.yaml" %}}
+
+This feature is also useful for running Jobs with sidecars, as the sidecar
+container will not prevent the Job from completing after the main container
+has finished.
+
+Here's an example of a Job with two containers, one of which is a sidecar:
+
+{{% codenew language="yaml" file="application/job/job-sidecar.yaml" %}}
+
+#### Resource sharing within containers
Given the ordering and execution for init containers, the following rules
for resource usage apply:
@@ -335,3 +375,4 @@ Kubernetes, consult the documentation for the version you are using.
* Learn how to [debug init containers](/docs/tasks/debug/debug-application/debug-init-containers/)
* Read about an overview of [kubelet](/docs/reference/command-line-tools-reference/kubelet/) and [kubectl](/docs/reference/kubectl/)
* Learn about the [types of probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe): liveness, readiness, startup probe.
+*
\ No newline at end of file
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 be6ea04cee..7a67737a2b 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
@@ -192,6 +192,7 @@ For a reference to old feature gates that are removed, please refer to
| `SecurityContextDeny` | `false` | Alpha | 1.27 | |
| `ServiceNodePortStaticSubrange` | `false` | Alpha | 1.27 | 1.27 |
| `ServiceNodePortStaticSubrange` | `true` | Beta | 1.28 | |
+| `SidecarContainers` | `false` | Alpha | 1.28 | |
| `SizeMemoryBackedVolumes` | `false` | Alpha | 1.20 | 1.21 |
| `SizeMemoryBackedVolumes` | `true` | Beta | 1.22 | |
| `StableLoadBalancerNodeGet` | `true` | Beta | 1.27 | |
@@ -701,6 +702,11 @@ Each feature gate is designed for enabling/disabling a specific feature:
risk of collision. See
[Avoiding collisions](/docs/concepts/services-networking/service/#avoiding-collisions)
for more details.
+- `SidecarContainers`: Allow setting the `restartPolicy` of an init container to
+ `Always` so that the container becomes a sidecar container (restartable init containers).
+ See
+ [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/init-containers/#sidecar-containers-and-restartpolicy)
+ for more details.
- `SizeMemoryBackedVolumes`: Enable kubelets to determine the size limit for
memory-backed volumes (mainly `emptyDir` volumes).
- `StableLoadBalancerNodeGet`: Enables less load balancer re-configurations by
@@ -749,4 +755,4 @@ Each feature gate is designed for enabling/disabling a specific feature:
feature, you will also need to enable any associated API resources.
For example, to enable a particular resource like
`storage.k8s.io/v1beta1/csistoragecapacities`, set `--runtime-config=storage.k8s.io/v1beta1/csistoragecapacities`.
- See [API Versioning](/docs/reference/using-api/#api-versioning) for more details on the command line flags.
+ See [API Versioning](/docs/reference/using-api/#api-versioning) for more details on the command line flags.
\ No newline at end of file
diff --git a/content/en/examples/application/deployment-sidecar.yaml b/content/en/examples/application/deployment-sidecar.yaml
new file mode 100644
index 0000000000..ae958c5b74
--- /dev/null
+++ b/content/en/examples/application/deployment-sidecar.yaml
@@ -0,0 +1,34 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+ name: myapp
+ labels:
+ app: myapp
+spec:
+ replicas: 1
+ selector:
+ matchLabels:
+ app: myapp
+ template:
+ metadata:
+ labels:
+ app: myapp
+ spec:
+ containers:
+ - name: myapp
+ image: alpine:latest
+ command: ['sh', '-c', 'echo "logging" > /opt/logs.txt']
+ volumeMounts:
+ - name: data
+ mountPath: /opt
+ initContainers:
+ - name: logshipper
+ image: alpine:latest
+ restartPolicy: Always
+ command: ['sh', '-c', 'tail /opt/logs.txt']
+ volumeMounts:
+ - name: data
+ mountPath: /opt
+ volumes:
+ - name: data
+ emptyDir: {}
\ No newline at end of file
diff --git a/content/en/examples/application/job/job-sidecar.yaml b/content/en/examples/application/job/job-sidecar.yaml
new file mode 100644
index 0000000000..c5518cb061
--- /dev/null
+++ b/content/en/examples/application/job/job-sidecar.yaml
@@ -0,0 +1,26 @@
+apiVersion: batch/v1
+kind: Job
+metadata:
+ name: myjob
+spec:
+ template:
+ spec:
+ containers:
+ - name: myjob
+ image: alpine:latest
+ command: ['sh', '-c', 'echo "logging" > /opt/logs.txt']
+ volumeMounts:
+ - name: data
+ mountPath: /opt
+ initContainers:
+ - name: logshipper
+ image: alpine:latest
+ restartPolicy: Always
+ command: ['sh', '-c', 'tail /opt/logs.txt']
+ volumeMounts:
+ - name: data
+ mountPath: /opt
+ restartPolicy: Never
+ volumes:
+ - name: data
+ emptyDir: {}
\ No newline at end of file
From 6c926cb5dbd20a3b72ec8a91431c99b08a65fd06 Mon Sep 17 00:00:00 2001
From: Patrick Ohly
Date: Mon, 3 Jul 2023 16:55:04 +0200
Subject: [PATCH 106/446] dra: update for Kubernetes 1.28
Several improvements under the hood which don't need to be documented here. API
changes (like storing generated resource claim names in the pod status) are
part of the generated API documentation.
What is worth mentioning because it was listed as "limitation" before is that
pre-scheduled pods are now supported better.
---
.../dynamic-resource-allocation.md | 36 +++++++++++++++----
1 file changed, 29 insertions(+), 7 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 f08eb3cf53..e4bc0eac98 100644
--- a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
+++ b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@@ -168,14 +168,36 @@ 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
+## Pre-scheduled Pods
-The scheduler plugin must be involved in scheduling Pods which use
-ResourceClaims. Bypassing the scheduler by setting the `nodeName` field leads
-to Pods that the kubelet refuses to start because the ResourceClaims are not
-reserved or not even allocated. It may be possible to [remove this
-limitation](https://github.com/kubernetes/kubernetes/issues/114005) in the
-future.
+When creating a Pod with `nodeName` already set, the scheduler gets bypassed.
+If some ResourceClaim needed by that Pod does not exist yet, is not allocated
+or not reserved for the Pod, then the kubelet will fail to run the Pod and
+re-check periodically because those requirements might still get fulfilled
+later.
+
+Such a situation can also arise when support for dynamic resource allocation
+was not enabled in the scheduler at the time when the Pod got scheduled
+(version skew, configuration, feature gate, etc.). kube-controller-manager
+detects this and tries to make the Pod runnable by triggering allocation and/or
+reserving the required ResourceClaims.
+
+However, it is better to avoid this because a Pod which is assigned to a node
+blocks normal resources (RAM, CPU) that then cannot be used for other Pods
+while the Pod is stuck. To make a Pod run on a specific node while still going
+through the normal scheduling flow, create the Pod with a node selector that
+matches exactly the desired node:
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+ name: pod-with-cats
+spec:
+ nodeSelector:
+ kubernetes.io/hostname: name-of-the-intended-node
+ ...
+```
## Enabling dynamic resource allocation
From cce3df22871c013d4b8014ee6b104c6af8621365 Mon Sep 17 00:00:00 2001
From: Francesco Romani
Date: Thu, 22 Jun 2023 08:53:48 +0200
Subject: [PATCH 107/446] node: podresources: GetAllocatable API is GA
move the feature gate to GA, fix the feature state to stable
Signed-off-by: Francesco Romani
---
.../compute-storage-net/device-plugins.md | 16 +---------------
.../feature-gates.md | 5 +++--
2 files changed, 4 insertions(+), 17 deletions(-)
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 7722d9ffa8..d61ba314a9 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
@@ -312,7 +312,7 @@ below:
### `GetAllocatableResources` gRPC endpoint {#grpc-endpoint-getallocatableresources}
-{{< feature-state state="beta" for_k8s_version="v1.23" >}}
+{{< feature-state state="stable" for_k8s_version="v1.28" >}}
GetAllocatableResources provides information on resources initially available on the worker node.
It provides more information than kubelet exports to APIServer.
@@ -338,16 +338,6 @@ message AllocatableResourcesResponse {
}
```
-Starting from Kubernetes v1.23, the `GetAllocatableResources` is enabled by default.
-You can disable it by turning off the `KubeletPodResourcesGetAllocatable`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
-
-Preceding Kubernetes v1.23, to enable this feature `kubelet` must be started with the following flag:
-
-```
---feature-gates=KubeletPodResourcesGetAllocatable=true
-```
-
`ContainerDevices` do expose the topology information declaring to which NUMA cells the device is
affine. The NUMA cells are identified using a opaque integer ID, which value is consistent to
what device plugins report
@@ -361,10 +351,6 @@ DaemonSet, `/var/lib/kubelet/pod-resources` must be mounted as a
{{< glossary_tooltip term_id="volume" >}} in the device monitoring agent's
[PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).
-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" >}}
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 6d70ba7544..66551a52a6 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
@@ -128,8 +128,6 @@ For a reference to old feature gates that are removed, please refer to
| `KubeletInUserNamespace` | `false` | Alpha | 1.22 | |
| `KubeletPodResourcesDynamicResources` | `false` | Alpha | 1.27 | |
| `KubeletPodResourcesGet` | `false` | Alpha | 1.27 | |
-| `KubeletPodResourcesGetAllocatable` | `false` | Alpha | 1.21 | 1.22 |
-| `KubeletPodResourcesGetAllocatable` | `true` | Beta | 1.23 | |
| `KubeletTracing` | `false` | Alpha | 1.25 | 1.26 |
| `KubeletTracing` | `true` | Beta | 1.27 | |
| `LegacyServiceAccountTokenCleanUp` | `false` | Alpha | 1.28 | |
@@ -290,6 +288,9 @@ For a reference to old feature gates that are removed, please refer to
| `KubeletPodResources` | `false` | Alpha | 1.13 | 1.14 |
| `KubeletPodResources` | `true` | Beta | 1.15 | 1.27 |
| `KubeletPodResources` | `true` | GA | 1.28 | - |
+| `KubeletPodResourcesGetAllocatable` | `false` | Alpha | 1.21 | 1.22 |
+| `KubeletPodResourcesGetAllocatable` | `true` | Beta | 1.23 | 1.27 |
+| `KubeletPodResourcesGetAllocatable` | `true` | GA | 1.28 | - |
| `LegacyServiceAccountTokenNoAutoGeneration` | `true` | Beta | 1.24 | 1.25 |
| `LegacyServiceAccountTokenNoAutoGeneration` | `true` | GA | 1.26 | - |
| `LegacyServiceAccountTokenTracking` | `false` | Alpha | 1.26 | 1.26 |
From 595925cb7dd490e1ea012bca5fd9a25680d07990 Mon Sep 17 00:00:00 2001
From: Shiming Zhang
Date: Tue, 25 Jul 2023 18:07:07 +0800
Subject: [PATCH 108/446] Docs update for Alpha PodHostIPs
---
content/en/docs/concepts/workloads/pods/downward-api.md | 9 ++++++++-
.../command-line-tools-reference/feature-gates.md | 3 +++
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/workloads/pods/downward-api.md b/content/en/docs/concepts/workloads/pods/downward-api.md
index 971475199c..e084c92abd 100644
--- a/content/en/docs/concepts/workloads/pods/downward-api.md
+++ b/content/en/docs/concepts/workloads/pods/downward-api.md
@@ -44,7 +44,7 @@ You can pass information from available Container-level fields using
### Information available via `fieldRef` {#downwardapi-fieldRef}
-For most Pod-level fields, you can provide them to a container either as
+For some Pod-level fields, you can provide them to a container either as
an environment variable or using a `downwardAPI` volume. The fields available
via either mechanism are:
@@ -75,9 +75,16 @@ The following information is available through environment variables
`status.hostIP`
: the primary IP address of the node to which the Pod is assigned
+`status.hostIPs`
+: the IP addresses is a dual-stack version of `status.hostIP`, the first is always the same as `status.hostIP`.
+ The field is available if you enable the `PodHostIPs` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
+
`status.podIP`
: the pod's primary IP address (usually, its IPv4 address)
+`status.podIPs`
+: the IP addresses is a dual-stack version of `status.podIP`, the first is always the same as `status.podIP`
+
The following information is available through a `downwardAPI` volume
`fieldRef`, **but not as environment variables**:
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 ae7593a78d..1dcc5fae07 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -165,6 +165,7 @@ For a reference to old feature gates that are removed, please refer to
| `PodDeletionCost` | `true` | Beta | 1.22 | |
| `PodDisruptionConditions` | `false` | Alpha | 1.25 | 1.25 |
| `PodDisruptionConditions` | `true` | Beta | 1.26 | |
+| `PodHostIPs` | `false` | Alpha | 1.28 | |
| `PodReadyToStartContainersCondition` | `false` | Alpha | 1.28 | |
| `PodSchedulingReadiness` | `false` | Alpha | 1.26 | 1.26 |
| `PodSchedulingReadiness` | `true` | Beta | 1.27 | |
@@ -655,6 +656,8 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `PodAndContainerStatsFromCRI`: Configure the kubelet to gather container and pod stats from the CRI container runtime rather than gathering them from cAdvisor.
As of 1.26, this also includes gathering metrics from CRI and emitting them over `/metrics/cadvisor` (rather than having cAdvisor emit them directly).
- `PodDisruptionConditions`: Enables support for appending a dedicated pod condition indicating that the pod is being deleted due to a disruption.
+- `PodHostIPs`: Enable the `status.hostIPs` field for pods and the {{< glossary_tooltip term_id="downward-api" text="downward API" >}}.
+ The field lets you expose host IP addresses to workloads.
- `PodIndexLabel`: Enables the Job controller and StatefulSet controller to add the pod index as a label when creating new pods. See [Job completion mode docs](/docs/concepts/workloads/controllers/job#completion-mode) and [StatefulSet pod index label docs](/docs/concepts/workloads/controllers/statefulset/#pod-index-label) for more details.
- `PodReadyToStartContainersCondition`: Enable the kubelet to mark the [PodReadyToStartContainers](/docs/concepts/workloads/pods/pod-lifecycle/#pod-has-network)
condition on pods. This was previously (1.25-1.27) known as `PodHasNetworkCondition`.
From 9e66b18a02129c0746963b5384fad89632aaf8b0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20Wo=C5=BAniak?=
Date: Fri, 21 Jul 2023 10:00:24 +0200
Subject: [PATCH 109/446] Job Backoff Limit per index review remarks
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Co-authored-by: Tim Bannister
Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
Co-authored-by: Paola Cortés <51036950+cortespao@users.noreply.github.com>
---
.../concepts/workloads/controllers/job.md | 74 ++++++++++++++-----
.../feature-gates.md | 4 +-
.../job-backoff-limit-per-index-example.yaml | 4 +-
3 files changed, 60 insertions(+), 22 deletions(-)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index b7e4c10c3f..d11213ee7b 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -318,9 +318,10 @@ caused by previous runs.
By default, each pod failure is counted towards the `.spec.backoffLimit` limit,
see [pod backoff failure policy](#pod-backoff-failure-policy). However, you can
customize handling of pod failures by setting the Job's [pod failure policy](#pod-failure-policy).
+
Additionally, you can choose to count the pod failures independently for each
-index of an Indexed Job by setting the `.spec.backoffLimitPerIndex` field
-(see [backoff limit per index](#backoff-limit-per-index)).
+index of an [Indexed](#completion-mode) Job by setting the `.spec.backoffLimitPerIndex` field
+(for more information, see [backoff limit per index](#backoff-limit-per-index)).
Note that even if you specify `.spec.parallelism = 1` and `.spec.completions = 1` and
`.spec.template.spec.restartPolicy = "Never"`, the same program may
@@ -371,34 +372,67 @@ from failed Jobs is not lost inadvertently.
{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
{{< note >}}
-You can only configure the backoff limit per index for a Job, if you
+You can only configure the backoff limit per index for an [Indexed](#completion-mode) Job, if you
have the `JobBackoffLimitPerIndex` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-enabled in your cluster. This feature is only available for Indexed Jobs, which
-use the `restartPolicy: Never`.
+enabled in your cluster.
{{< /note >}}
-When you run an Indexed Job, you may want to handle pod failures for different
-indexes as counted independently. To do so, set the `.spec.backoffLimitPerIndex`
-to specify the the maximal number of pod failures per index. When the number is
-exceeded for an index, the index is marked as failed in the
-`.status.failedIndexes` field. Note that, a failing index does not interrupt
-execution of other indexes. You can additionally limit the maximal number of
-indexes marked failed by setting the `.spec.maxFailedIndexes` field. In that case,
-the the number of failed indexes is exceeded, then the entire Job is marked
-failed and execution all pods and indexed is terminated.
+When you run an [indexed](#completion-mode) Job, you can choose to handle retries
+for pod failures independently for each index. To do so, set the
+`.spec.backoffLimitPerIndex` to specify the the maximal number of pod failures
+per index.
-When all indexes finishes for a Job using this feature, and there is at least
-one failed index, then the entire Job is marked as failed, even if some indexes
-are finished successfully.
+When the per-index backoff limit is exceeded for an index, Kuberentes considers the index as failed and adds it to the
+`.status.failedIndexes` field. The succeeded indexes, those with a successfully
+executed pods, are recorded in the `.status.completedIndexes` field, regardless of whether you set
+the `backoffLimitPerIndex` field.
-Here is a manifest for an Indexed Job that defines a `backoffLimitPerIndex`:
+Note that a failing index does not interrupt execution of other indexes.
+Once all indexes finish for a Job where you specified a backoff limit per index,
+if at least one of those indexes did fail, the Job controller marks the overall
+Job as failed, by setting the Failed condition in the status. The Job gets
+marked as failed even if some, potentially nearly all, of the indexes were
+processed successfully.
+
+You can additionally limit the maximal number of indexes marked failed by
+setting the `.spec.maxFailedIndexes` field.
+When the number of failed indexes exceeds the `maxFailedIndexes` field, the
+Job controller triggers termination of all remaining running Pods for that Job.
+Once all pods are terminated, the entire Job is marked failed by the Job
+controller, by setting the Failed condition in the Job status.
+
+Here is an example manifest for a Job that defines a `backoffLimitPerIndex`:
{{< codenew file="/controllers/job-backoff-limit-per-index-example.yaml" >}}
-In the example above, the Job controller will allow for one restart for each
+In the example above, the Job controller allows for one restart for each
of the indexes. When the total number of failed indexes exceeds 5, then
the entire Job is terminated.
+Once the job is finished, the the Job status looks as follows:
+
+```sh
+kubectl get -o yaml job job-backoff-limit-per-index-example
+```
+
+```yaml
+ status:
+ completedIndexes: 1,3,5,7,9
+ failedIndexes: 0,2,4,6,8
+ succeeded: 5 # 1 succeeded pod for each of 5 succeeded indexes
+ failed: 10 # 2 failed pods (1 retry) for each of 5 failed indexes
+ conditions:
+ - message: Job has failed indexes
+ reason: FailedIndexes
+ status: "True"
+ type: Failed
+```
+
+Additionally, you may want to use the per-index backoff along with a
+[pod failure policy](#pod-failure-policy). When using
+per-index backoff, there is a new `FailIndex` action available which allows you to
+avoid unnecessary retries within an index.
+
### Pod failure policy {#pod-failure-policy}
{{< feature-state for_k8s_version="v1.26" state="beta" >}}
@@ -481,6 +515,8 @@ These are some requirements and semantics of the API:
should not be incremented and a replacement Pod should be created.
- `Count`: use to indicate that the Pod should be handled in the default way.
The counter towards the `.spec.backoffLimit` should be incremented.
+ - `FailIndex`: use this action along with [backoff limit per index](#backoff-limit-per-index)
+ to avoid unnecessary retries within the index of a failed pod.
{{< note >}}
When you use a `podFailurePolicy`, the job controller only matches Pods in 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 04c1f891bb..da3d15be37 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
@@ -118,7 +118,7 @@ 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 | |
-| `JobBackoffLimitPerIndex` | `false` | Alpha | 1.28 | 1.28 |
+| `JobBackoffLimitPerIndex` | `false` | Alpha | 1.28 | |
| `JobPodFailurePolicy` | `false` | Alpha | 1.25 | 1.25 |
| `JobPodFailurePolicy` | `true` | Beta | 1.26 | |
| `JobReadyPods` | `false` | Alpha | 1.23 | 1.23 |
@@ -552,7 +552,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
and volume controllers.
- `JobMutableNodeSchedulingDirectives`: Allows updating node scheduling directives in
the pod template of [Job](/docs/concepts/workloads/controllers/job).
-- `JobBackoffLimitPerIndex`: Allows users to specify the maximal number of pod
+- `JobBackoffLimitPerIndex`: Allows specifying the maximal number of pod
retries per index in Indexed jobs.
- `JobPodFailurePolicy`: Allow users to specify handling of pod failures based on container
exit codes and pod conditions.
diff --git a/content/en/examples/controllers/job-backoff-limit-per-index-example.yaml b/content/en/examples/controllers/job-backoff-limit-per-index-example.yaml
index 5b229458d5..c238479f90 100644
--- a/content/en/examples/controllers/job-backoff-limit-per-index-example.yaml
+++ b/content/en/examples/controllers/job-backoff-limit-per-index-example.yaml
@@ -14,7 +14,9 @@ spec:
containers:
- name: example
image: python
- command:
+ command: # The jobs fails as there is at least one failed index
+ # (all even indexes fail in here), yet all indexes
+ # are executed as maxFailedIndexes is not exceeded.
- python3
- -c
- |
From 4568e6d9a403242dd8b8acc46b64bef30cfb2882 Mon Sep 17 00:00:00 2001
From: Itamar Holder
Date: Thu, 3 Aug 2023 21:24:29 +0300
Subject: [PATCH 110/446] Document NodeSwap graduation to Beta1
Signed-off-by: Itamar Holder
---
.../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 820cb088dc..59d6df201f 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
@@ -153,7 +153,8 @@ For a reference to old feature gates that are removed, please refer to
| `NodeInclusionPolicyInPodTopologySpread` | `false` | Alpha | 1.25 | 1.25 |
| `NodeInclusionPolicyInPodTopologySpread` | `true` | Beta | 1.26 | |
| `NodeLogQuery` | `false` | Alpha | 1.27 | |
-| `NodeSwap` | `false` | Alpha | 1.22 | |
+| `NodeSwap` | `false` | Alpha | 1.22 | 1.27 |
+| `NodeSwap` | `false` | Beta1 | 1.28 | |
| `OpenAPIEnums` | `false` | Alpha | 1.23 | 1.23 |
| `OpenAPIEnums` | `true` | Beta | 1.24 | |
| `PDBUnhealthyPodEvictionPolicy` | `false` | Alpha | 1.26 | 1.26 |
From b56c82c714283df3239d254c8eeb85bc85571ed5 Mon Sep 17 00:00:00 2001
From: Itamar Holder
Date: Wed, 19 Jul 2023 18:03:40 +0300
Subject: [PATCH 111/446] Update content/en/docs/concepts/architecture/nodes.md
Signed-off-by: Itamar Holder
---
.../en/docs/concepts/architecture/nodes.md | 43 +++++++++++--------
1 file changed, 25 insertions(+), 18 deletions(-)
diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md
index 370f58ac16..4f2f7983c9 100644
--- a/content/en/docs/concepts/architecture/nodes.md
+++ b/content/en/docs/concepts/architecture/nodes.md
@@ -617,11 +617,7 @@ During a non-graceful shutdown, Pods are terminated in the two phases:
## Swap memory management {#swap-memory}
-{{< feature-state state="alpha" for_k8s_version="v1.22" >}}
-
-Prior to Kubernetes 1.22, nodes did not support the use of swap memory, and a
-kubelet would by default fail to start if swap was detected on a node. In 1.22
-onwards, swap memory support can be enabled on a per-node basis.
+{{< feature-state state="beta" for_k8s_version="v1.28" >}}
To enable swap on a node, the `NodeSwap` feature gate must be enabled on
the kubelet, and the `--fail-swap-on` command line flag or `failSwapOn`
@@ -638,29 +634,40 @@ specify how a node will use swap memory. For example,
```yaml
memorySwap:
- swapBehavior: LimitedSwap
+ swapBehavior: UnlimitedSwap
```
-The available configuration options for `swapBehavior` are:
-
-- `LimitedSwap`: Kubernetes workloads are limited in how much swap they can
- use. Workloads on the node not managed by Kubernetes can still swap.
-- `UnlimitedSwap`: Kubernetes workloads can use as much swap memory as they
+- `UnlimitedSwap` (default): Kubernetes workloads can use as much swap memory as they
request, up to the system limit.
+- `LimitedSwap`: The utilization of swap memory by Kubernetes workloads is subject to limitations. Only Pods of Burstable QoS are permitted to employ swap.
If configuration for `memorySwap` is not specified and the feature gate is
enabled, by default the kubelet will apply the same behaviour as the
-`LimitedSwap` setting.
+`UnlimitedSwap` setting.
-The behaviour of the `LimitedSwap` setting depends if the node is running with
-v1 or v2 of control groups (also known as "cgroups"):
+With `LimitedSwap`, Pods that do not fall under the Burstable QoS classification (i.e.
+`BestEffort`/`Guaranteed` Qos Pods) are prohibited from utilizing swap memory.
+To maintain the aforementioned security and node
+health guarantees, these Pods are not permitted to use swap memory when `LimitedSwap` is
+in effect.
-- **cgroupsv1:** Kubernetes workloads can use any combination of memory and
- swap, up to the pod's memory limit, if set.
-- **cgroupsv2:** Kubernetes workloads cannot use swap memory.
+Prior to detailing the calculation of the swap limit, it is necessary to define the following terms:
+* `nodeTotalMemory`: The total amount of physical memory available on the node.
+* `totalPodsSwapAvailable`: The total amount of swap memory on the node that is available for use by Pods (some swap memory may be reserved for system use).
+* `containerMemoryRequest`: The container's memory request.
+
+Swap limitation is configured as:
+`(containerMemoryRequest / nodeTotalMemory) * totalPodsSwapAvailable`.
+
+It is important to note that, for containers within Burstable QoS Pods, it is possible to
+opt-out of swap usage by specifying memory requests that are equal to memory limits.
+Containers configured in this manner will not have access to swap memory.
+
+Swap is supported only with **cgroup v2**, cgroup v1 is not supported.
For more information, and to assist with testing and provide feedback, please
-see [KEP-2400](https://github.com/kubernetes/enhancements/issues/2400) and its
+see the blog-post about [Kubernetes 1.28: NodeSwap graduates to Beta1](/blog/2023/07/18/swap-beta1-1.28-2023/),
+[KEP-2400](https://github.com/kubernetes/enhancements/issues/4128) and its
[design proposal](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2400-node-swap/README.md).
## {{% heading "whatsnext" %}}
From 0084a6315060d53f727dac07f56fc132a61e228a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Roman=20Bedn=C3=A1=C5=99?=
Date: Fri, 4 Aug 2023 03:02:21 +0200
Subject: [PATCH 112/446] Add docs for PersistentVolume last phase transition
time (#42008)
---
.../en/docs/concepts/storage/persistent-volumes.md | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index dfa08602f8..6886b8740c 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -768,6 +768,20 @@ A volume will be in one of the following phases:
The CLI will show the name of the PVC bound to the PV.
+#### Phase transition timestamp
+
+{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
+
+Persistent volume status contains `lastPhaseTransitionTime` field which holds
+a timestamp of when the volume last transitioned its phase. For newly created
+volumes the phase is set to "Pending" and `lastPhaseTransitionTime` is set to
+current time.
+
+{{< note >}}
+You need to enable the `PersistentVolumeLastPhaseTransitionTime` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+to see `lastPhaseTransitionTime` field.
+{{< /note >}}
+
## PersistentVolumeClaims
Each PVC contains a spec and status, which is the specification and status of the claim.
From 77bdf58549b68f8db3558c57ee2fee9d220c5f2e Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Fri, 4 Aug 2023 14:51:54 +1000
Subject: [PATCH 113/446] add kubernetes 1.28 release blog
Signed-off-by: Brad McCoy
---
.../_posts/2023-08-04-kubernetes-1.28-blog.md | 290 ++++++++++++++++++
1 file changed, 290 insertions(+)
create mode 100644 content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
new file mode 100644
index 0000000000..94fd0cddff
--- /dev/null
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -0,0 +1,290 @@
+---
+layout: blog
+title: "Kubernetes v1.28: "
+date: 2023-08-02
+slug: kubernetes-v1-28-release
+---
+
+**Authors**: [Kubernetes v1.28 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.28/release-team.md)
+
+Announcing the release of Kubernetes v1.28 , the second release of 2023!
+
+This release consists of 46 enhancements. 20 of those enhancements are entering Alpha, 14 are graduating to Beta, and 12 are graduating to Stable.
+
+## Release Theme And Logo
+
+**Kubernetes v1.28: **
+
+The theme for Kubernetes v1.28 is **.
+
+{{< figure src="/images/blog/2023-07-02-kubernetes-1.28-blog/kubernetes-1.28.png" alt="Kubernetes 1.28 logo" class="release-logo" >}}
+
+Talk about release - waiting for the theme
+
+Special thanks to [someone](https://www.some-link) for creating the logo.
+
+# What's New (Major Themes)
+
+## CRD Validation Rules
+
+This [Common Expression Language (CEL)](https://github.com/google/cel-go) can be used to validate custom resources. The primary goal is to allow the majority of the validation use cases that currently must be handled by a webhook, to instead be handled by adding inline validation expressions directly into the schema of a CRD.
+
+CRDs need direct support for non-trivial validation. While admission webhooks do support CRDs validation, they significantly complicate the development and operability of CRDs.
+
+This KEP proposes that an inline expression language be integrated directly into CRDs such that a much larger portion of validation use cases can be solved without the use of webhooks. When selecting an expression language, we want to be sure that it can support defaulting and CRD conversion in the future.
+
+It is sufficiently lightweight and safe to be run directly in the kube-apiserver (since CRD creation is a privileged operation), has a straight-forward and unsurprising grammar, and supports pre-parsing and type checking of expressions, allowing syntax and type errors to be caught at CRD registration time.
+
+## Common Expression Language For Admission Control
+
+Common Expression language for admission control is customizable, in-process validation of requests to the Kubernetes API server as an alternative to validating admission webhooks.
+
+This builds on the capabilities of the CRD Validation Rules feature that graduated to beta in 1.25 but with a focus on the policy enforcement capabilities of validating admission control.
+
+This will lower the infrastructure barrier to enforcing customizable policies as well as providing primitives that help the community establish and adhere to the best practices of both K8s and its extensions.
+
+## Admission Webhook Match Conditions
+
+Introduce CEL expression filters to webhooks, to allow webhooks to be scoped more narrowly.
+
+This adds "match conditions" to admission webhooks, as an extension to the existing rules to define the scope of a webhook. A matchCondition is a CEL expression that must evaluate to true for the admission request to be sent to the webhook. If a matchCondition evaluates to false, the webhook is skipped for that request (implicitly allowed).
+
+ValidatingAdmissionPolicy is an exciting new feature that we hope will greatly reduce the need for admission webhooks, but it is intentionally not attempting to cover every possible use case. This proposal aims to improve the situation for those webhooks that cannot be migrated.
+
+## Unknown Version Interoperability Proxy
+
+When a cluster has multiple API servers at mixed versions (such as during an upgrade/downgrade or when runtime-config changes and a rollout happens), not every apiserver can serve every resource at every version.
+
+To fix this, the filter is added to the handler chain in the aggregator which proxies clients to an API server that is capable of handling their request.
+
+When an upgrade or downgrade is performed on a cluster, for some period of time the api servers are at differing versions and are able to serve different sets of built-in resources (different groups, versions, and resources are all possible).
+
+## CRD Validation Ratcheting
+
+This Allows CRs to fail validation if the patch did not alter any of the invalid fields. The ability to shift left validation logic from controllers to the front end is a long-term goal for improving the useability of the Kubernetes project.
+
+## Add Generic Control Plane Staging Repositories
+
+This factors the kube-apiserver to build on a new staging repository that consumes k/apiserver but has a bigger, carefully chosen subset of the functionality of kube-apiserver such that it is reusable.
+
+The factoring will be progressive: we will start with a new repo that adds
+nothing to k/apiserver, and then progressively move generic functionality from
+kube-apiserver to the new repository. The new repo will be named
+k/generic-controlplane.
+
+## CDI Support To The Device Plugin API
+
+CDI provides a standardized way of injecting complex devices into a container (i.e. devices that logically require more than just a single /dev node to be injected for them to work). This new feature enables plugin developers to utilize the CDIDevices field added to the CRI in 1.27 to pass CDI devices directly to CDI enabled runtimes (of which containerd and crio-o are in recent releases).
+
+## Sidecar Containers Built-in Support
+
+This introduces a restartPolicy field to init containers and uses it to indicate that an init container is a sidecar container. Kubelet will start init containers with restartPolicy=Always in the order with other init containers, but instead of waiting for its completion, it will wait for the container startup completion.
+
+The condition for startup completion will be that the startup probe succeeded (or if no startup probe is defined) and postStart handler is completed. This condition is represented with the field Started of ContainerStatus type. See the section "Pod startup completed condition" for considerations on picking this signal.
+
+The field restartPolicy will only be accepted on init containers. The only supported value now is Always. No other values will be defined. Moreover, the field will be nullable so the default value will be "no value".
+
+Other values for restartPolicy of containers will not be accepted and containers will follow the logic currently implemented.
+
+Sidecar containers will not block Pod completion - if all regular containers are complete, sidecar containers will be terminated.
+
+During the sidecar startup stage, the restart behavior will be similar to init containers. If the Pod restartPolicy is Never, the sidecar container that failed during startup will NOT be restarted and the whole Pod will fail. If the Pod restartPolicy is Always or OnFailure, it will be restarted.
+
+Once the sidecar container is started (postStart completed and startup probe succeeded), these containers will be restarted even when the Pod restartPolicy is Never or OnFailure. Furthermore, sidecar containers will be restarted even during Pod termination.
+
+In order to minimize OOM kills of sidecar containers, the OOM adjustment for these containers will match or exceed the OOM score adjustment of regular containers in the Pod.
+
+This also enables sidecar containers (those will not be allowed for other init containers):
+
+- PostStart and PreStop lifecycle handlers for sidecar containers
+- All probes (startup, readiness, liveness)
+
+Readiness probes of sidecars will contribute to determining the whole Pod readiness.
+
+## Node System Memory Swap Support
+
+This adds swap support to nodes in a controlled, predictable manner so that Kubernetes users can perform testing and provide data to continue building cluster capabilities on top of swap.
+
+There are two distinct types of users for swap, who may overlap:
+
+- Node administrators, who may want swap available for node-level performance tuning and stability/reducing noisy neighbor issues.
+
+- Application developers, who have written applications that would benefit from using swap memory. There are hence a number of possible ways that one could envision swap use on a node.
+
+## Add Support To Handle Non-graceful Node Shutdown
+
+This feature allows stateful workloads to restart on a different node if the original node is shut down unexpectedly or ends up in a non-recoverable state perhaps due to hardware failure or unresponsive OS.
+
+This allows stateful workloads to failover to a different node successfully after the original node is shut down or in a non-recoverable state such as the hardware failure or broken OS.
+
+The Graceful Node Shutdown introduces a way to detect a node shutdown and handle it gracefully. However, a node shutdown action may not be detected by Kubelet's Node Shutdown Manager, either because the command does not trigger the inhibitor locks mechanism used by Kubelet or because of a user error, i.e., the ShutdownGracePeriod and ShutdownGracePeriodCriticalPods are not configured properly.
+
+When a node is shutdown but not detected by Kubelet's Node Shutdown Manager, the pods that are part of a StatefulSet will be stuck in terminating status on the shutdown node and cannot move to a new running node. This is because Kubelet on the shutdown node is not available to delete the pods so the StatefulSet cannot create a new pod with the same name. If there are volumes used by the pods, the VolumeAttachments will not be deleted from the original shutdown node so the volumes used by these pods cannot be attached to a new running node. As a result, the application running on the StatefulSet cannot function properly. If the original shutdown node comes up, the pods will be deleted by Kubelet and new pods will be created on a different running node. If the original shutdown node does not come up, these pods will be stuck in terminating status on the shutdown node forever.
+
+This handles node shutdown cases that are not detected by Kubelet's Node Shutdown Manager. The pods will be forcefully deleted in this case, triggering the deletion of the VolumeAttachments, and new pods will be created on a new running node so that application can continue to function.
+
+## Retroactive Default StorageClass Assignment
+
+This feature makes it easier to change the default StorageClass by allowing the default storage class assignment to be retroactive for existing unbound persistent volume claims without any storage class assigned.
+
+This changes the behavior of default storage class assignment to be retroactive for existing unbound persistent volume claims without any storage class assigned. This changes the existing Kubernetes behavior slightly, which is further described in the sections below.
+
+When a user needs to provision storage they create a PVC to request a volume. A control loop looks for any new PVCs and based on the current state of the cluster the volume will be provided using one of the following methods:
+
+Static provisioning - PVC did not specify any storage class and there is already an existing PV that can be bound to it.
+Dynamic provisioning - there is no existing PV that could be bound but PVC did specify a storage class or there is exactly one storage class in the cluster marked as default.
+Considering the "normal" operation described above there are additional cases that can be problematic:
+
+It’s hard to mark a different SC as the default one. Cluster admin can choose between two bad solutions:
+
+Option 1: Cluster has two default SCs for a short time, i.e. admin marks the new default SC as default and then marks the old default SC as non-default. When there are two default SCs in a cluster, the PVC admission plugin refuses to accept new PVCs with pvc.spec.storageClassName = nil. Hence, cluster users may get errors when creating PVCs at the wrong time. They must know it’s a transient error and manually retry later.
+
+Option 2: Cluster has no default SC for a short time, i.e. admin marks the old default SC as non-default and then marks the new default SC as default. Since there is no default SC for some time, PVCs with pvc.spec.storageClassName = nil created during this time will not get any SC and are Pending forever. Users must be smart enough to delete the PVC and re-create it.
+
+When users want to change the default SC parameters, they must delete the SC and re-create it, Kubernetes API does not allow change in the SC. So there is no default SC for some time and the second case above applies here too. Re-creating the storage class to change parameters can be useful in cases where there is a quota set for the SC, and since the quota is coupled with the SC name users can not use Option 1 because the second SC would have a different name and so the existing quota would not apply to it.
+
+Defined ordering during cluster installation. Kubernetes cluster installation tools must be currently smart enough to create a default SC before starting anything that may create PVCs that need it. If such a tool supports multiple cloud providers, storage backends, and add-ons that require storage (such as an image registry), it may be quite complicated to do the ordering right.
+
+## Support The Oldest Node And Newest Control Plane
+
+This enables testing and expanding the supported skew between core node and control plane components by one version from n-2 to n-3, so that node components (kubelet and kube-proxy) for the oldest supported minor version work with control plane components (kube-apiserver, kube-scheduler, kube-controller-manager, cloud-controller-manager) for the newest supported minor version.
+
+The Kubernetes yearly support period already makes annual upgrades possible. Users can upgrade to the latest patch versions to pick up security fixes and do 3 sequential minor version upgrades once a year to "catch up" to the latest supported minor version.
+
+However, since the tested/supported skew between nodes and control planes is currently limited to 2 versions, a 3-version upgrade would have to update nodes twice to stay within the supported skew. For example, to upgrade from v1.40 to v1.43:
+
+Begin: control plane and nodes on v1.40
+Control plane upgrade: v1.40 → v1.41 → v1.42
+Node upgrades: v1.40 → v1.42
+Control plane upgrade: v1.42 → v1.43
+Node upgrades: v1.42 → v1.43
+
+Node upgrades are inherently more disruptive than control plane upgrades to workloads, for several reasons:
+
+Workloads can be designed to have no dependencies on the Kubernetes control plane, so Kubernetes control plane availability does not directly impact running pods
+There can be many more nodes (hundreds to thousands) than control plane members (typically 1 or 3).
+
+Every time nodes are upgraded to a new minor version, every pod running on those nodes must be drained/rescheduled. This is true for immutable nodes and mutable/bare-metal nodes. If all nodes are being upgraded, this means every pod in the cluster will be replaced at least once. Patch updates of kubelet / kube-proxy components can be done in place, so it is possible to pick up security fixes and patch updates less disruptively.
+
+Replacing or moving pods that are slow to stop or start or have significant data gravity takes significant time, so it is desirable to minimize how frequently that must be done.
+If node/control plane skew support was expanded so the oldest node components work with the newest control plane components, the example upgrade path from v1.40 to v1.43 above could improve this:
+
+Begin: control plane and nodes on v1.40
+Control plane upgrade: v1.40 → v1.41 → v1.42 → v1.43
+Node upgrades: v1.40 → v1.43
+
+## Pod Replacement Policy
+
+This enables a new field for the Job API that allows for users to specify if they want replacement Pods as soon as the previous Pods are terminating (existing behavior) or only once the existing pods are fully terminated (new behavior).
+
+Many common machine learning frameworks, such as Tensorflow and JAX, require unique pods per Index. Currently, if a pod enters a terminating state (due to preemption, eviction or other external factors), a replacement pod is created and immediately fails to start.
+
+Having a replacement Pod before the previous one fully terminates can also cause problems in clusters with scarce resources or with tight budgets. These resources can be difficult to obtain so pods can take a long time to find resources and they may only be able to find nodes once the existing pods have been terminated. If cluster autoscaler is enabled, the replacement Pods might produce undesired scale-ups.
+
+On the other hand, if a replacement Pod is not immediately created, the Job status would show that the number of active pods doesn't match the desired parallelism. To provide better visibility, the job status can have a new field to track the number of Pods currently terminating.
+
+This new field can also be used by queueing controllers, such as Kueue, to track the number of terminating pods to calculate quotas.
+
+## Backoff Limit Per Index
+
+This extends the Job API to support indexed jobs where the backoff limit is per index, and the Job can continue execution despite some of its indexes failing.
+
+Currently, the indexes of an indexed job share a single backoff limit. When the job reaches this shared backoff limit, the job controller marks the entire job as failed, and the resources are cleaned up, including indexes that have yet to run to completion.
+
+As a result, the current implementation does not cover the situation where the workload is truly embarrassingly parallel and each index is independent of other indexes.
+
+For instance, if indexed jobs were used as the basis for a suite of long-running integration tests, then each test run would only be able to find a single test failure.
+
+Other popular batch services like AWS Batch use a separate backoff limit for each index, showing that this is a common use case that should be supported by Kubernetes.
+
+We propose a new policy for running Indexed Jobs in which the backoff limit controls the number of retries per index. When the new policy is used all indexes execute until their success or failure. We also propose a new API field to control the number of failed indexes.
+
+Additionally, we propose a new action in PodFailurePolicy, called FailIndex, to short-circuit the failing of the index before the backoff limit per index is reached.
+
+## cAdvisor-less, CRI-full Container And Pod Stats
+
+This encompasses two related pieces of work (summary API and /metrics/cadvisor), and will require changes in three different components (CRI implementation, Kubelet, cAdvisor).
+
+There are two main APIs that consumers use to gather stats about running containers and pods: summary API and /metrics/cadvisor. The Kubelet is responsible for implementing the summary API, and cadvisor is responsible for fulfilling /metrics/cadvisor.
+
+This aims to enhance CRI implementations to be able to fulfill all the stats needs of Kubernetes. At a high level, there are two pieces of this:
+
+- Enhance the CRI API with enough metrics to be able to supplement the pod and container fields in the summary API directly from CRI.
+
+- Enhance the CRI implementations to broadcast the required metrics to fulfill the pod and container fields in the /metrics/cadvisor endpoint.
+
+## Feature Graduations And Deprecations In Kubernetes v1.28
+### Graduations to stable
+
+This release includes a total of 12 enhancements promoted to Stable:
+
+* [Kubectl Events](https://github.com/kubernetes/enhancements/issues/1440)
+* [Retroactive default StorageClass assignment](https://github.com/kubernetes/enhancements/issues/3333)
+* [Non-graceful node shutdown](https://github.com/kubernetes/enhancements/issues/2268)
+* [Support 3rd party device monitoring plugins](https://github.com/kubernetes/enhancements/issues/606)
+* [Auth API to get self-user attributes](https://github.com/kubernetes/enhancements/issues/3325)
+* [Proxy Terminating Endpoints](https://github.com/kubernetes/enhancements/issues/1669)
+* [Expanded DNS Configuration](https://github.com/kubernetes/enhancements/issues/2595)
+* [Cleaning up IPTables Chain Ownership](https://github.com/kubernetes/enhancements/issues/3178)
+* [Minimizing iptables-restore input size](https://github.com/kubernetes/enhancements/issues/3453)
+* [Graduate the kubelet pod resources endpoint to GA](https://github.com/kubernetes/enhancements/issues/3743)
+* [Extend podresources API to report allocatable resources](https://github.com/kubernetes/enhancements/issues/2403)
+* [Move EndpointSlice Reconciler into Staging](https://github.com/kubernetes/enhancements/issues/3685)
+
+### Deprecations And Removals
+
+This release saw several removals:
+
+* [Removal of CSI Migration for GCE PD](https://github.com/kubernetes/enhancements/issues/1488)
+
+## Release Notes
+
+The complete details of the Kubernetes v1.28 release are available in our [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.28.md).
+
+## Availability
+
+Kubernetes v1.28 is available for download on [GitHub](https://github.com/kubernetes/kubernetes/releases/tag/v1.28.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.28 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.
+
+We would like to thank the entire release team for the hours spent hard at work to ensure we deliver a solid Kubernetes v1.28 release for our community.
+
+Special thanks to our Release Lead, Grace Nguyen, for guiding us through a smooth and successful release cycle and facilitating the communication and collaboration between the different Release Teams taking advantage of her experience as a Shadow and Lead in these teams.
+
+## Ecosystem Updates
+
+* KubeCon + CloudNativeCon North America 2023 will take place in Chicago, Illinois, The United States of America, from 6 – 9 November 2023! You can find more information about the conference and registration on the [event site](https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/).
+
+## 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.28 release cycle, which [ran for 14 weeks](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.28) (May 15 to August 15), we saw contributions from [911 companies](https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1&var-period_name=v1.27.0%20-%20now&var-metric=contributions) and [1440 individuals](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=v1.27.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.28 release team on Friday, September 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-v128-release/) 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).
From e7141ef1b34028898d855ce9487bafb2f5d55c42 Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Fri, 4 Aug 2023 20:12:51 +1000
Subject: [PATCH 114/446] add China kubecon to ecosystem updates
Signed-off-by: Brad McCoy
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 94fd0cddff..a595cda9c6 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -255,6 +255,7 @@ Special thanks to our Release Lead, Grace Nguyen, for guiding us through a smoot
## Ecosystem Updates
+* KubeCon + CloudNativeCon China 2023 will take place in Shanghai, China, from 26 – 28 September 2023! You can find more information about the conference and registration on the [event site](https://www.lfasiallc.com/kubecon-cloudnativecon-open-source-summit-china/).
* KubeCon + CloudNativeCon North America 2023 will take place in Chicago, Illinois, The United States of America, from 6 – 9 November 2023! You can find more information about the conference and registration on the [event site](https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/).
## Project Velocity
From fa73830e0b4159f2a31fd7a144f1c05bbec4e61b Mon Sep 17 00:00:00 2001
From: Markus Lehtonen
Date: Fri, 4 Aug 2023 14:06:35 +0300
Subject: [PATCH 115/446] docs: another change of wording of k8s versioning
---
.../docs/setup/production-environment/container-runtimes.md | 6 +++---
.../administer-cluster/kubeadm/configure-cgroup-driver.md | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/en/docs/setup/production-environment/container-runtimes.md b/content/en/docs/setup/production-environment/container-runtimes.md
index 36bf4ef299..957b8d3c0f 100644
--- a/content/en/docs/setup/production-environment/container-runtimes.md
+++ b/content/en/docs/setup/production-environment/container-runtimes.md
@@ -157,7 +157,7 @@ Starting with v1.22 and later, when creating a cluster with kubeadm, if the user
the `cgroupDriver` field under `KubeletConfiguration`, kubeadm defaults it to `systemd`.
{{< /note >}}
-In Kubernetes {{< skew currentVersion >}}, with the `KubeletCgroupDriverFromCRI`
+In Kubernetes v1.28, with the `KubeletCgroupDriverFromCRI`
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
enabled and a container runtime that supports the `RuntimeConfig` CRI RPC,
the kubelet automatically detects the appropriate cgroup driver from the runtime,
@@ -257,7 +257,7 @@ sudo systemctl restart containerd
When using kubeadm, manually configure the
[cgroup driver for kubelet](/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver/#configuring-the-kubelet-cgroup-driver).
-In Kubernetes {{< skew currentVersion >}}, you can enable automatic detection of the
+In Kubernetes v1.28, you can enable automatic detection of the
cgroup driver as an alpha feature. See [systemd cgroup driver](#systemd-cgroup-driver)
for more details.
@@ -302,7 +302,7 @@ You should also note the changed `conmon_cgroup`, which has to be set to the val
cgroup driver configuration of the kubelet (usually done via kubeadm) and CRI-O
in sync.
-In Kubernetes {{< skew currentVersion >}}, you can enable automatic detection of the
+In Kubernetes v1.28, you can enable automatic detection of the
cgroup driver as an alpha feature. See [systemd cgroup driver](#systemd-cgroup-driver)
for more details.
diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
index afaa370011..b811985819 100644
--- a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
+++ b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md
@@ -37,7 +37,7 @@ driver of the kubelet.
In v1.22 and later, if the user does not set the `cgroupDriver` field under `KubeletConfiguration`,
kubeadm defaults it to `systemd`.
-In Kubernetes {{< skew currentVersion >}}, you can enable automatic detection of the
+In Kubernetes v1.28, you can enable automatic detection of the
cgroup driver as an alpha feature.
See [systemd cgroup driver](/docs/setup/production-environment/container-runtimes/#systemd-cgroup-driver)
for more details.
From 367bf076340235b9ad28f4d423f8047ede3ad5c9 Mon Sep 17 00:00:00 2001
From: Aldo Culquicondor
Date: Fri, 4 Aug 2023 11:32:27 -0400
Subject: [PATCH 116/446] Tracking with finalizers is always enabled
---
.../concepts/workloads/controllers/job.md | 20 -------------------
1 file changed, 20 deletions(-)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 2ccbaefdb1..9becd24b7b 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -831,32 +831,12 @@ mismatch.
{{< feature-state for_k8s_version="v1.26" state="stable" >}}
-{{< note >}}
-The control plane doesn't track Jobs using finalizers, if the Jobs were created
-when the feature gate `JobTrackingWithFinalizers` was disabled, even after you
-upgrade the control plane to 1.26.
-{{< /note >}}
-
The control plane keeps track of the Pods that belong to any Job and notices if
any such Pod is removed from the API server. To do that, the Job controller
creates Pods with the finalizer `batch.kubernetes.io/job-tracking`. The
controller removes the finalizer only after the Pod has been accounted for in
the Job status, allowing the Pod to be removed by other controllers or users.
-Jobs created before upgrading to Kubernetes 1.26 or before the feature gate
-`JobTrackingWithFinalizers` is enabled are tracked without the use of Pod
-finalizers.
-The Job {{< glossary_tooltip term_id="controller" text="controller" >}} updates
-the status counters for `succeeded` and `failed` Pods based only on the Pods
-that exist in the cluster. The contol plane can lose track of the progress of
-the Job if Pods are deleted from the cluster.
-
-You can determine if the control plane is tracking a Job using Pod finalizers by
-checking if the Job has the annotation
-`batch.kubernetes.io/job-tracking`. You should **not** manually add or remove
-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" >}}
From 16566d6affe0cc03b5234cf5f2c502831c2c9b5e Mon Sep 17 00:00:00 2001
From: Aldo Culquicondor
Date: Fri, 4 Aug 2023 11:50:54 -0400
Subject: [PATCH 117/446] Update deprecation status of job-tracking annotation
---
.../reference/labels-annotations-taints/_index.md | 13 +++----------
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index 63114d9fbc..b2c0ec9aec 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -1094,17 +1094,10 @@ Example: `batch.kubernetes.io/job-tracking: ""`
Used on: Jobs
-The presence of this annotation on a Job indicates that the control plane is
+The presence of this annotation on a Job used to indicate that the control plane is
[tracking the Job status using finalizers](/docs/concepts/workloads/controllers/job/#job-tracking-with-finalizers).
-The control plane uses this annotation to safely transition to tracking Jobs
-using finalizers, while the feature is in development.
-You should **not** manually add or remove this annotation.
-
-{{< note >}}
-Starting from Kubernetes 1.26, this annotation is deprecated.
-Kubernetes 1.27 and newer will ignore this annotation and always track Jobs
-using finalizers.
-{{< /note >}}
+Adding or removing this annotation no longer has an effect (Kubernetes v1.27 and later)
+All Jobs are tracked with finalizers.
### job-name (deprecated) {#job-name}
From 894da22c87e7a0de71aa6afdf7f47c9dbc1393df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marko=20Mudrini=C4=87?=
Date: Fri, 4 Aug 2023 20:43:41 +0200
Subject: [PATCH 118/446] Add blog post for pkgs.k8s.io
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Marko Mudrinić
---
.../2023-08-15-pkgs-k8s-io-introduction.md | 205 ++++++++++++++++++
1 file changed, 205 insertions(+)
create mode 100644 content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md
diff --git a/content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md b/content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md
new file mode 100644
index 0000000000..7a46ad78f6
--- /dev/null
+++ b/content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md
@@ -0,0 +1,205 @@
+---
+layout: blog
+title: "pkgs.k8s.io: Introducing Kubernetes community-owned package repositories"
+date: 2023-08-15
+slug: pkgs-k8s-io-introduction
+---
+
+**Author**: Marko Mudrinić (Kubermatic)
+
+We're very excited to introduce the Kubernetes community-owned package
+repositories for Debian and RPM packages: `pkgs.k8s.io`! The new package
+repositories are replacement for the Google-hosted package repositories
+(`apt.kubernetes.io` and `yum.kubernetes.io`) that we've been using since
+Kubernetes v1.5.
+
+This blog post contains information about these new package repositories,
+what does it mean to you as an end user, and how to migrate to the new
+repositories.
+
+## What you need to know about the new package repositories?
+
+- This is an **opt-in change**, you're required to manually migrate from the
+ Google-hosted repository to the Kubernetes community-owned repositories.
+ See below for migration information and instructions.
+- Access to the Google-hosted repository will remain intact for the foreseeable
+ future. However, the Kubernetes project plans to stop publishing packages to
+ the Google-hosted repository in the future. The project strongly recommends
+ migrating to the Kubernetes package repositories going forward.
+- The Kubernetes package repositories contain packages beginning with those
+ Kubernetes versions that were still under support when the community took
+ over the package builds. This means that anything before v1.24.0 will only be
+ available in the Google-hosted repository.
+- There's a dedicated package repository for each Kubernetes minor version.
+ When upgrading to to a different minor release, you must bear in mind that
+ the package repository details also change.
+
+## Why are we introducing new package repositories?
+
+As the Kubernetes project is growing, we want to ensure the best possible
+experience for the end users. The Google-hosted repository has been serving
+us well for many years, but we started facing some problems that require
+significant changes to how we publish packages. Another goal that we have is to
+use community-owned infrastructure for all critical components and that
+includes package repositories.
+
+Publishing packages to the Google-hosted repository is a manual process that
+can be done only by a team of Google employees called
+[Google Build Admins](/releases/release-managers/#build-admins).
+[The Kubernetes Release Managers team](/releases/release-managers/#release-managers)
+is a very diverse team especially in terms of timezones that we work in.
+Given this constraint, we have to do very careful planning for every release to
+ensure that we have both Release Manager and Google Build Admin available to
+carry out the release.
+
+Another problem is that we only have a single package repository. Because of
+this, we were not able to publish packages for prerelease versions (alpha,
+beta, and rc). This made testing Kubernetes prereleases harder for anyone who
+is interested to do so. The feedback that we receive from people testing these
+releases is critical to ensure the best quality of releases, so we want to make
+testing these releases as easy as possible. On top of that, having only one
+repository limited us when it comes to publishing dependencies like `cri-tools`
+and `kubernetes-cni`.
+
+Regardless of all these issues, we're very thankful to Google and Google Build
+Admins for their involvement, support, and help all these years!
+
+## How the new package repositories work?
+
+The new package repositories are hosted at `pkgs.k8s.io` for both Debian and
+RPM packages. At this time, this domain points to a CloudFront CDN backed by S3
+bucket that contains repositories and packages. However, we plan on onboarding
+additional mirrors in the future, giving possibility for other companies to
+help us with serving packages.
+
+Packages are built and published via the [OpenBuildService (OBS) platform](http://openbuildservice.org).
+After a long period of evaluating different solutions, we made a decision to
+use OpenBuildService as a platform to manage our repositories and packages.
+First of all, OpenBuildService is an open source platform used by a large
+number of open source projects and companies, like openSUSE, VideoLAN,
+Dell, Intel, and more. OpenBuildService has many features making it very
+flexible and easy to integrate with our existing release tooling. It also
+allows us to build packages in a similar way as for the Google-hosted
+repository making the migration process as seamless as possible.
+
+SUSE sponsors the Kubernetes project with access to their reference
+OpenBuildService setup ([`build.opensuse.org`](http://build.opensuse.org)) and
+with technical support to integrate OBS with our release processes.
+
+We use SUSE's OBS instance for building and publishing packages. Upon building
+a new release, our tooling automatically pushes needed artifacts and
+package specifications to `build.opensuse.org`. That will trigger the build
+process that's going to build packages for all supported architectures (AMD64,
+ARM64, PPC64LE, S390X). At the end, generated packages will be automatically
+pushed to our community-owned S3 bucket making them available to all users.
+
+We want to take this opportunity to thank SUSE for allowing us to use
+`build.opensuse.org` and their generous support to make this integration
+possible!
+
+## What are significant differences between the Google-hosted and Kubernetes package repositories?
+
+There are three significant differences that you should be aware of:
+
+- There's a dedicated package repository for each Kubernetes minor release.
+ For example, repository called `core:/stable:/v1.28` only hosts packages for
+ stable Kubernetes v1.28 releases. This means you can install v1.28.0 from
+ this repository, but you can't install v1.27.0 or any other minor release
+ other then v1.28. Upon upgrading to another minor version, you have to add a
+ new repository and optionally remove the old one
+- There's a difference in what `cri-tools` and `kubernetes-cni` package
+ versions are available in each Kubernetes repository
+ - These two packages are dependencies for `kubelet` and `kubeadm`
+ - Kubernetes repositories for v1.24 to v1.27 have same versions of these
+ packages as the Google-hosted repository
+ - Kubernetes repositories for v1.28 and onwards are going to have published
+ only versions that are used by that Kubernetes minor release
+ - Speaking of v1.28, only kubernetes-cni 1.2.0 and cri-tols v1.28 are going
+ to be available in the repository for Kubernetes v1.28
+ - Similar for v1.29, we only plan on publishing cri-tools v1.29 and
+ whatever kubernetes-cni version is going to be used by Kubernetes v1.29
+- The revision part of the package version (the `-00` part in `1.28.0-00`) is
+ now autogenerated by the OpenBuildService platform and has a different format.
+ The revision is now in the format of `-x.y`, e.g. `1.28.0-1.1`
+
+## Does this in any way affect existing Google-hosted repositories?
+
+The Google-hosted repository and all packages published to it will continue
+working in the same way as before. There are no changes in how we build and
+publish packages to the Google-hosted repository, all newly-introduced changes
+are only affecting packages publish to the community-owned repositories.
+
+However, as mentioned at the beginning of this blog post, we plan to stop
+publishing packages to the Google-hosted repository in the future.
+
+## How to migrate to the Kubernetes community-owned repositories?
+
+### Debian, Ubuntu, and operating systems using `apt`/`apt-get`
+
+1. Replace the `apt` repository definition so that `apt` points to the new
+ repository instead of the Google-hosted repository. Make sure to replace the
+ Kubernetes minor version in the command below with your the minor version
+ that you're currently using:
+
+ ```shell
+ echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.28/deb/ /" | sudo tee /etc/apt/sources.list.d/kubernetes.list
+ ```
+
+2. Download the public signing key for the Kubernetes package repositories.
+ The same signing key is used for all repositories so you can disregard the
+ version in the URL:
+
+ ```shell
+ curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.28/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
+ ```
+
+3. Update the `apt` package index:
+
+ ```shell
+ sudo apt-get update
+ ```
+
+### CentOS, Fedora, RHEL, and operating systems using `rpm`/`dnf`
+
+1. Replace the `yum` repository definition so that `yum` points to the new
+ repository instead of the Google-hosted repository. Make sure to replace the
+ Kubernetes minor version in the command below with your the minor version
+ that you're currently using:
+
+```shell
+cat <
Date: Sat, 5 Aug 2023 00:34:31 +0530
Subject: [PATCH 119/446] Implemented single column list for metrics page
---
assets/scss/_custom.scss | 78 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
diff --git a/assets/scss/_custom.scss b/assets/scss/_custom.scss
index 1660b74c31..832c6a0c2d 100644
--- a/assets/scss/_custom.scss
+++ b/assets/scss/_custom.scss
@@ -354,6 +354,84 @@ main {
word-break: break-word;
}
+ $table-caption: "This is the list of STABLE metrics emitted from core Kubernetes components";
+
+// If any more parameters are needed in future , Define them here
+$labels: (
+ "Name",
+ "Stability Level",
+ "Type",
+ "Help",
+ "Labels",
+ "Const Labels",
+ "Deprecated Version"
+);
+
+// Define a mixin for the key-value pair style
+@mixin key-value-pair {
+ td {
+ padding: 5px 10px;
+ font-weight: bold;
+ text-align: left;
+ width: 100%;
+ position: relative;
+ &:nth-child(odd) {
+ font-style: italic;
+ }
+ // Pseudo-class 'before' FOR EDITING THE LABELS MAKE EDITS HERE
+ &::before {
+ content: "";
+ display: inline;
+ position: absolute;
+ left: 0;
+ padding-bottom: 10em;
+ }
+ }
+}
+
+// Apply the key-value pair style to the table
+table.metrics {
+ border-collapse: collapse;
+ width: 100%;
+ margin-top: 20px;
+ caption {
+ font-size: 1.2em;
+ font-weight: bold;
+ padding-bottom: 10px;
+ border-bottom: 2px solid #333;
+ }
+ thead {
+ display: none; // Hide the table header
+ }
+ tbody {
+ tr.metric {
+ td {
+ @include key-value-pair;
+ display: block;
+ margin-bottom: 10px;
+ .metric_labels,
+ .metric_const_labels,
+ .metric_deprecated_version {
+ display: block;
+ position: relative;
+ }
+ }
+ // Cycles through all the labels and places them one after the other
+ $i: 1;
+ // Use @each to iterate through the labels and apply the mixin
+ @each $label in $labels {
+ td:nth-child(#{$i})::before {
+ content: "#{$label}:"; // Add the label content
+ font-weight: 800; // Set font weight 800 for all labels
+ margin-right: 5px; // Adds a margin on the right of the label
+ }
+ $i: $i + 1;
+ }
+ }
+ }
+}
+
+
table.no-word-break td,
table.no-word-break code {
word-break: normal;
From 69a4031d17b5a3f5f565e18957a9f592d9269b1d Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:27:50 +1000
Subject: [PATCH 120/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 94fd0cddff..493ce826f7 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -51,7 +51,7 @@ This adds "match conditions" to admission webhooks, as an extension to the exist
ValidatingAdmissionPolicy is an exciting new feature that we hope will greatly reduce the need for admission webhooks, but it is intentionally not attempting to cover every possible use case. This proposal aims to improve the situation for those webhooks that cannot be migrated.
-## Unknown Version Interoperability Proxy
+## Mixed version proxy
When a cluster has multiple API servers at mixed versions (such as during an upgrade/downgrade or when runtime-config changes and a rollout happens), not every apiserver can serve every resource at every version.
From d2d62b9cb7211132c118bdc055467b59f93acbcc Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:28:04 +1000
Subject: [PATCH 121/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 493ce826f7..8a83af8fc0 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -76,7 +76,7 @@ k/generic-controlplane.
CDI provides a standardized way of injecting complex devices into a container (i.e. devices that logically require more than just a single /dev node to be injected for them to work). This new feature enables plugin developers to utilize the CDIDevices field added to the CRI in 1.27 to pass CDI devices directly to CDI enabled runtimes (of which containerd and crio-o are in recent releases).
-## Sidecar Containers Built-in Support
+## API awareness of sidecar containers (alpha)
This introduces a restartPolicy field to init containers and uses it to indicate that an init container is a sidecar container. Kubelet will start init containers with restartPolicy=Always in the order with other init containers, but instead of waiting for its completion, it will wait for the container startup completion.
From 278e84bb00224d5c288243205055ad14abeff9df Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:35:28 +1000
Subject: [PATCH 122/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 8a83af8fc0..02dbd0ccdb 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -25,7 +25,7 @@ Special thanks to [someone](https://www.some-link) for creating the logo.
# What's New (Major Themes)
-## CRD Validation Rules
+## Improvements to CustomResourceDefinition validation expressions
This [Common Expression Language (CEL)](https://github.com/google/cel-go) can be used to validate custom resources. The primary goal is to allow the majority of the validation use cases that currently must be handled by a webhook, to instead be handled by adding inline validation expressions directly into the schema of a CRD.
From f4d217e2e77fcff8848b12ebc36bffcd58afb76a Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:35:39 +1000
Subject: [PATCH 123/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 02dbd0ccdb..61e0378705 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -35,7 +35,7 @@ This KEP proposes that an inline expression language be integrated directly into
It is sufficiently lightweight and safe to be run directly in the kube-apiserver (since CRD creation is a privileged operation), has a straight-forward and unsurprising grammar, and supports pre-parsing and type checking of expressions, allowing syntax and type errors to be caught at CRD registration time.
-## Common Expression Language For Admission Control
+## ValidatingAdmissionPolicies graduate to beta
Common Expression language for admission control is customizable, in-process validation of requests to the Kubernetes API server as an alternative to validating admission webhooks.
From 3b451c7daf1b2622924cfaf1522ade4ce2761bc7 Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:35:50 +1000
Subject: [PATCH 124/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 61e0378705..6ca13223ca 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -43,7 +43,7 @@ This builds on the capabilities of the CRD Validation Rules feature that graduat
This will lower the infrastructure barrier to enforcing customizable policies as well as providing primitives that help the community establish and adhere to the best practices of both K8s and its extensions.
-## Admission Webhook Match Conditions
+## Match conditions for admission webhooks
Introduce CEL expression filters to webhooks, to allow webhooks to be scoped more narrowly.
From 1b5b49e5961b5aea36c0a20b58550413660cb61d Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:36:30 +1000
Subject: [PATCH 125/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 6ca13223ca..92a8c2c7ca 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -86,7 +86,8 @@ The field restartPolicy will only be accepted on init containers. The only suppo
Other values for restartPolicy of containers will not be accepted and containers will follow the logic currently implemented.
-Sidecar containers will not block Pod completion - if all regular containers are complete, sidecar containers will be terminated.
+Sidecar containers do not block Pod completion: if all regular containers are complete, sidecar
+containers in that Pod will be terminated.
During the sidecar startup stage, the restart behavior will be similar to init containers. If the Pod restartPolicy is Never, the sidecar container that failed during startup will NOT be restarted and the whole Pod will fail. If the Pod restartPolicy is Always or OnFailure, it will be restarted.
From dcc799da4daf8f6747d5fc1f2a05172bd49a5e09 Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:36:39 +1000
Subject: [PATCH 126/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 92a8c2c7ca..73282bece8 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -82,9 +82,8 @@ This introduces a restartPolicy field to init containers and uses it to indicate
The condition for startup completion will be that the startup probe succeeded (or if no startup probe is defined) and postStart handler is completed. This condition is represented with the field Started of ContainerStatus type. See the section "Pod startup completed condition" for considerations on picking this signal.
-The field restartPolicy will only be accepted on init containers. The only supported value now is Always. No other values will be defined. Moreover, the field will be nullable so the default value will be "no value".
-
-Other values for restartPolicy of containers will not be accepted and containers will follow the logic currently implemented.
+For init containers, you can either omit the `restartPolicy` field, or set it to `Always`. Omitting the field
+means that you want a true init container that runs to completion before application startup.
Sidecar containers do not block Pod completion: if all regular containers are complete, sidecar
containers in that Pod will be terminated.
From e0dc2d3a34b7e130b444681c2f06b68c697cc510 Mon Sep 17 00:00:00 2001
From: Brad McCoy
Date: Sat, 5 Aug 2023 07:37:03 +1000
Subject: [PATCH 127/446] Update
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
Co-authored-by: Tim Bannister
---
content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
index 73282bece8..204b634fe3 100644
--- a/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
+++ b/content/en/blog/_posts/2023-08-04-kubernetes-1.28-blog.md
@@ -78,7 +78,9 @@ CDI provides a standardized way of injecting complex devices into a container (i
## API awareness of sidecar containers (alpha)
-This introduces a restartPolicy field to init containers and uses it to indicate that an init container is a sidecar container. Kubelet will start init containers with restartPolicy=Always in the order with other init containers, but instead of waiting for its completion, it will wait for the container startup completion.
+Kubernetes 1.28 introduces an alpha `restartPolicy` field for [init containers](/docs/concepts/workloads/pods/init-containers/),
+and uses that to indicate when an init container is also a _sidecar container_. The will start init containers with `restartPolicy: Always` in the order they are defined, along with other init containers. Instead of waiting for that sidecar container to complete before starting the main container(s) for the Pod, the kubelet only waits for
+the sidecar init container to have started.
The condition for startup completion will be that the startup probe succeeded (or if no startup probe is defined) and postStart handler is completed. This condition is represented with the field Started of ContainerStatus type. See the section "Pod startup completed condition" for considerations on picking this signal.
From efd907b5a61c67fba9ee05409107fb1ec74ee0e9 Mon Sep 17 00:00:00 2001
From: Gauravpadam <1032201077@tcetmumbai.in>
Date: Sat, 5 Aug 2023 12:47:17 +0530
Subject: [PATCH 128/446] Removed css dependency to modify the page
---
assets/scss/_custom.scss | 52 ++++++++++------------------------------
1 file changed, 12 insertions(+), 40 deletions(-)
diff --git a/assets/scss/_custom.scss b/assets/scss/_custom.scss
index 832c6a0c2d..617c31ab1c 100644
--- a/assets/scss/_custom.scss
+++ b/assets/scss/_custom.scss
@@ -354,18 +354,10 @@ main {
word-break: break-word;
}
- $table-caption: "This is the list of STABLE metrics emitted from core Kubernetes components";
+/* SCSS Related to the Metrics Table */
-// If any more parameters are needed in future , Define them here
-$labels: (
- "Name",
- "Stability Level",
- "Type",
- "Help",
- "Labels",
- "Const Labels",
- "Deprecated Version"
-);
+// Define the variable for the table caption
+$table-caption: "This is the list of STABLE metrics emitted from core Kubernetes components";
// Define a mixin for the key-value pair style
@mixin key-value-pair {
@@ -374,18 +366,9 @@ $labels: (
font-weight: bold;
text-align: left;
width: 100%;
- position: relative;
&:nth-child(odd) {
font-style: italic;
}
- // Pseudo-class 'before' FOR EDITING THE LABELS MAKE EDITS HERE
- &::before {
- content: "";
- display: inline;
- position: absolute;
- left: 0;
- padding-bottom: 10em;
- }
}
}
@@ -398,10 +381,14 @@ table.metrics {
font-size: 1.2em;
font-weight: bold;
padding-bottom: 10px;
- border-bottom: 2px solid #333;
}
thead {
- display: none; // Hide the table header
+ tr{
+ th{
+ display: block;
+ width: 100%;
+ }
+ }
}
tbody {
tr.metric {
@@ -409,35 +396,20 @@ table.metrics {
@include key-value-pair;
display: block;
margin-bottom: 10px;
- .metric_labels,
- .metric_const_labels,
- .metric_deprecated_version {
- display: block;
- position: relative;
- }
}
- // Cycles through all the labels and places them one after the other
- $i: 1;
- // Use @each to iterate through the labels and apply the mixin
- @each $label in $labels {
- td:nth-child(#{$i})::before {
- content: "#{$label}:"; // Add the label content
- font-weight: 800; // Set font weight 800 for all labels
- margin-right: 5px; // Adds a margin on the right of the label
- }
- $i: $i + 1;
+ td.metric_name {
+ font-weight: 700;
}
}
}
}
-
table.no-word-break td,
table.no-word-break code {
word-break: normal;
}
-}
+}
// blockquotes and callouts
From 1544b191ba89677dd5ce66d2f84097ae761bc770 Mon Sep 17 00:00:00 2001
From: Arhell
Date: Sat, 5 Aug 2023 10:19:37 +0300
Subject: [PATCH 129/446] [ja] Remove obsolete references
---
.../tools/kubeadm/create-cluster-kubeadm.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md b/content/ja/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
index 36b197a629..55bf57fbc8 100644
--- a/content/ja/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
+++ b/content/ja/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
@@ -328,7 +328,7 @@ kubectl --kubeconfig ./admin.conf get nodes
{{< note >}}
上の例では、rootユーザーに対するSSH接続が有効であることを仮定しています。もしそうでない場合は、`admin.conf`ファイルを誰か他のユーザーからアクセスできるようにコピーした上で、代わりにそのユーザーを使って`scp`してください。
-`admin.conf`ファイルはユーザーにクラスターに対する _特権ユーザー_ の権限を与えます。そのため、このファイルを使うのは控えめにしなければなりません。通常のユーザーには、明示的に許可した権限を持つユニークなクレデンシャルを生成することを推奨します。これには、`kubeadm alpha kubeconfig user --client-name `コマンドが使えます。このコマンドを実行すると、KubeConfigファイルがSTDOUTに出力されるので、ファイルに保存してユーザーに配布します。その後、`kubectl create (cluster)rolebinding`コマンドを使って権限を付与します。
+`admin.conf`ファイルはユーザーにクラスターに対する _特権ユーザー_ の権限を与えます。そのため、このファイルを使うのは控えめにしなければなりません。通常のユーザーには、明示的に許可した権限を持つユニークなクレデンシャルを生成することを推奨します。これには、`kubeadm kubeconfig user --client-name `コマンドが使えます。このコマンドを実行すると、KubeConfigファイルがSTDOUTに出力されるので、ファイルに保存してユーザーに配布します。その後、`kubectl create (cluster)rolebinding`コマンドを使って権限を付与します。
{{< /note >}}
### (オプション)APIサーバーをlocalhostへプロキシする
From e135f05006af3cc1c3c2aac522640b74cb62f5c3 Mon Sep 17 00:00:00 2001
From: Gauravpadam <1032201077@tcetmumbai.in>
Date: Sat, 5 Aug 2023 15:56:13 +0530
Subject: [PATCH 130/446] indexing for readers ; Improved formatting
---
assets/scss/_custom.scss | 29 ++++++++++++++++++++++-------
1 file changed, 22 insertions(+), 7 deletions(-)
diff --git a/assets/scss/_custom.scss b/assets/scss/_custom.scss
index 617c31ab1c..a295128a13 100644
--- a/assets/scss/_custom.scss
+++ b/assets/scss/_custom.scss
@@ -363,12 +363,8 @@ $table-caption: "This is the list of STABLE metrics emitted from core Kubernetes
@mixin key-value-pair {
td {
padding: 5px 10px;
- font-weight: bold;
text-align: left;
width: 100%;
- &:nth-child(odd) {
- font-style: italic;
- }
}
}
@@ -376,17 +372,23 @@ $table-caption: "This is the list of STABLE metrics emitted from core Kubernetes
table.metrics {
border-collapse: collapse;
width: 100%;
- margin-top: 20px;
caption {
font-size: 1.2em;
font-weight: bold;
padding-bottom: 10px;
}
thead {
+ border: 1px solid $medium-grey;
+ display: flex;
+ flex-direction: column;
+ width: fit-content;
+ margin-bottom: 1rem;
+
tr{
+ display: contents;
th{
display: block;
- width: 100%;
+ white-space: nowrap;
}
}
}
@@ -395,11 +397,24 @@ table.metrics {
td {
@include key-value-pair;
display: block;
- margin-bottom: 10px;
+ margin-bottom: 1rem;
+ min-width: 2rem;
}
td.metric_name {
font-weight: 700;
}
+ td.metric_labels_varying{
+ div {
+ position: relative;
+ padding-left: 1em;
+
+ &::before{
+ content: '-';
+ position: absolute;
+ left:0;
+ }
+ }
+ }
}
}
}
From dc9e07cb0333f734e6ed2a6439a8fdf93f32febc Mon Sep 17 00:00:00 2001
From: Karthik-PM
Date: Sat, 5 Aug 2023 16:39:52 +0530
Subject: [PATCH 131/446] added .editorconfig
---
content/en/docs/contribute/style/style-guide.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/content/en/docs/contribute/style/style-guide.md b/content/en/docs/contribute/style/style-guide.md
index f9367dd0c5..5972409087 100644
--- a/content/en/docs/contribute/style/style-guide.md
+++ b/content/en/docs/contribute/style/style-guide.md
@@ -651,6 +651,12 @@ You can remove ... | You can easily remove ...
These steps ... | These simple steps ...
{{< /table >}}
+### EditorConfig
+The Kubernetes project maintains an EditorConfig file that sets common style preferences in text editors
+such as VS Code. You can use this file if you want to ensure that your contributions are consistent with
+the rest of the project. To view the file, refer to
+[`.editorconfig`](https://github.com/kubernetes/website/blob/main/.editorconfig) in the repository root.
+
## {{% heading "whatsnext" %}}
* Learn about [writing a new topic](/docs/contribute/style/write-new-topic/).
From 057d18ec404aa2ef9397097ee4f19b3992d777cb Mon Sep 17 00:00:00 2001
From: Tim Bannister
Date: Sat, 5 Aug 2023 13:40:17 +0100
Subject: [PATCH 132/446] Update deprecation mentions
Match how existing lists are doing it
---
content/en/docs/concepts/storage/persistent-volumes.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index 770bc4d29a..1e105bfcc7 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -375,7 +375,7 @@ the following types of volumes:
* {{< glossary_tooltip text="csi" term_id="csi" >}}
* flexVolume (deprecated)
* gcePersistentDisk
-* rbd ( **deprecated** in v1.28)
+* rbd (deprecated)
* portworxVolume
You can only expand a PVC if its storage class's `allowVolumeExpansion` field is set to true.
@@ -954,7 +954,7 @@ applicable:
* iSCSI
* Local volume
* OpenStack Cinder
-* RBD (Ceph Block Device) ( **deprecated** in v1.28)
+* RBD (deprecated)
* VsphereVolume
### PersistentVolume using a Raw Block Volume {#persistent-volume-using-a-raw-block-volume}
From 24d8bd52287a84f068aede53a9fb6c9e31bf75f4 Mon Sep 17 00:00:00 2001
From: Tim Bannister
Date: Sat, 5 Aug 2023 13:40:57 +0100
Subject: [PATCH 133/446] Update deprecation suggestions
Use different language for out-of-project and in-project alternatives
---
content/en/docs/concepts/storage/volumes.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index 46167eb9f2..d8a409cb00 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -193,7 +193,8 @@ and the kubelet, set the `InTreePluginAzureFileUnregister` flag to `true`.
{{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
{{< note >}}
-The Kubernetes project recommends to use [CephFS CSI](https://github.com/ceph/ceph-csi) out-of-tree driver instead.
+The Kubernetes project suggests that you use the [CephFS CSI](https://github.com/ceph/ceph-csi) third party
+storage driver instead.
{{< /note >}}
A `cephfs` volume allows an existing CephFS volume to be
@@ -873,7 +874,8 @@ directory. For more details, see [projected volumes](/docs/concepts/storage/proj
{{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
{{< note >}}
-The Kubernetes project recommends to use [Ceph RBD CSI](https://github.com/ceph/ceph-csi) out-of-tree driver instead.
+The Kubernetes project suggests that you use the [Ceph CSI](https://github.com/ceph/ceph-csi)
+third party storage driver instead, in RBD mode.
{{< /note >}}
An `rbd` volume allows a
@@ -953,7 +955,8 @@ For more details, see [Configuring Secrets](/docs/concepts/configuration/secret/
### vsphereVolume (deprecated) {#vspherevolume}
{{< note >}}
-The Kubernetes project recommends to use vSphere CSI out-of-tree driver instead.
+The Kubernetes project recommends using the [vSphere CSI](https://github.com/kubernetes-sigs/vsphere-csi-driver)
+out-of-tree storage driver instead.
{{< /note >}}
A `vsphereVolume` is used to mount a vSphere VMDK volume into your Pod. The contents
From 9a5cc446bafa729e037f479432458aa8b8dda206 Mon Sep 17 00:00:00 2001
From: pprokop
Date: Thu, 27 Jul 2023 08:53:17 +0200
Subject: [PATCH 134/446] Update feature-gates availibilty for
TopologyManagerPolicyOptions
Signed-off-by: pprokop
---
.../reference/command-line-tools-reference/feature-gates.md | 6 ++++--
1 file changed, 4 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 e96f8793ba..2a75e9636f 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
@@ -201,8 +201,10 @@ For a reference to old feature gates that are removed, please refer to
| `TopologyAwareHints` | `false` | Beta | 1.23 | 1.23 |
| `TopologyAwareHints` | `true` | Beta | 1.24 | |
| `TopologyManagerPolicyAlphaOptions` | `false` | Alpha | 1.26 | |
-| `TopologyManagerPolicyBetaOptions` | `false` | Beta | 1.26 | |
-| `TopologyManagerPolicyOptions` | `false` | Alpha | 1.26 | |
+| `TopologyManagerPolicyBetaOptions` | `false` | Beta | 1.26 | 1.27 |
+| `TopologyManagerPolicyBetaOptions` | `true` | Beta | 1.28 | |
+| `TopologyManagerPolicyOptions` | `false` | Alpha | 1.26 | 1.27 |
+| `TopologyManagerPolicyOptions` | `true` | Beta | 1.28 | |
| `UnknownVersionInteroperabilityProxy` | `false` | Alpha | 1.28 | |
| `UserNamespacesStatelessPodsSupport` | `false` | Alpha | 1.25 | |
| `ValidatingAdmissionPolicy` | `false` | Alpha | 1.26 | |
From 7b13d1f0b7e7b3d6110c40a992d310d090080c9d Mon Sep 17 00:00:00 2001
From: Arhell
Date: Sun, 6 Aug 2023 00:39:51 +0300
Subject: [PATCH 135/446] [id] Remove obsolete references
---
.../tools/kubeadm/create-cluster-kubeadm.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/id/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md b/content/id/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
index c05757cbba..f6053a131d 100644
--- a/content/id/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
+++ b/content/id/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md
@@ -492,7 +492,7 @@ dan `scp` menggunakan pengguna lain tersebut.
Berkas `admin.conf` memberikan penggunanya privilese (_privilege_) _superuser_ terhadap klaster.
Berkas ini harus digunakan seperlunya. Untuk pengguna biasa, direkomendasikan
untuk membuat kredensial unik dengan privilese _whitelist_. Kamu dapat melakukan
-ini dengan perintah `kubeadm alpha kubeconfig user --client-name `.
+ini dengan perintah `kubeadm kubeconfig user --client-name `.
Perintah tersebut akan mencetak berkas KubeConfig ke STDOUT yang harus kamu simpan
ke dalam sebuah berkas dan mendistribusikannya pada para pengguna. Setelah itu, whitelist
privilese menggunakan `kubectl create (cluster)rolebinding`.
From fda6a61c672061f7dc6cd37ae18daa19179f9133 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marko=20Mudrini=C4=87?=
Date: Sat, 5 Aug 2023 23:52:41 +0200
Subject: [PATCH 136/446] Fix review comments
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Marko Mudrinić
---
.../blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md b/content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md
index 7a46ad78f6..e6644433b2 100644
--- a/content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md
+++ b/content/en/blog/_posts/2023-08-15-pkgs-k8s-io-introduction.md
@@ -31,7 +31,7 @@ repositories.
over the package builds. This means that anything before v1.24.0 will only be
available in the Google-hosted repository.
- There's a dedicated package repository for each Kubernetes minor version.
- When upgrading to to a different minor release, you must bear in mind that
+ When upgrading to a different minor release, you must bear in mind that
the package repository details also change.
## Why are we introducing new package repositories?
@@ -105,7 +105,7 @@ There are three significant differences that you should be aware of:
For example, repository called `core:/stable:/v1.28` only hosts packages for
stable Kubernetes v1.28 releases. This means you can install v1.28.0 from
this repository, but you can't install v1.27.0 or any other minor release
- other then v1.28. Upon upgrading to another minor version, you have to add a
+ other than v1.28. Upon upgrading to another minor version, you have to add a
new repository and optionally remove the old one
- There's a difference in what `cri-tools` and `kubernetes-cni` package
versions are available in each Kubernetes repository
@@ -138,7 +138,7 @@ publishing packages to the Google-hosted repository in the future.
1. Replace the `apt` repository definition so that `apt` points to the new
repository instead of the Google-hosted repository. Make sure to replace the
- Kubernetes minor version in the command below with your the minor version
+ Kubernetes minor version in the command below with the minor version
that you're currently using:
```shell
@@ -146,7 +146,7 @@ publishing packages to the Google-hosted repository in the future.
```
2. Download the public signing key for the Kubernetes package repositories.
- The same signing key is used for all repositories so you can disregard the
+ The same signing key is used for all repositories, so you can disregard the
version in the URL:
```shell
@@ -163,7 +163,7 @@ publishing packages to the Google-hosted repository in the future.
1. Replace the `yum` repository definition so that `yum` points to the new
repository instead of the Google-hosted repository. Make sure to replace the
- Kubernetes minor version in the command below with your the minor version
+ Kubernetes minor version in the command below with the minor version
that you're currently using:
```shell
From 6cc095bf81bb1b0c3b41c285194ed0674794a4c6 Mon Sep 17 00:00:00 2001
From: Gauravpadam <1032201077@tcetmumbai.in>
Date: Sun, 6 Aug 2023 14:45:05 +0530
Subject: [PATCH 137/446] Improves current appearence
---
assets/scss/_custom.scss | 79 ++++++++++++----------------------------
1 file changed, 24 insertions(+), 55 deletions(-)
diff --git a/assets/scss/_custom.scss b/assets/scss/_custom.scss
index a295128a13..fa53a99a04 100644
--- a/assets/scss/_custom.scss
+++ b/assets/scss/_custom.scss
@@ -356,74 +356,43 @@ main {
/* SCSS Related to the Metrics Table */
-// Define the variable for the table caption
-$table-caption: "This is the list of STABLE metrics emitted from core Kubernetes components";
+ @media (max-width: 767px) { // for mobile devices, Display the names, Stability levels & types
-// Define a mixin for the key-value pair style
-@mixin key-value-pair {
- td {
- padding: 5px 10px;
- text-align: left;
- width: 100%;
- }
-}
+ th:nth-child(n + 4),
+ td:nth-child(n + 4) {
+ display: none;
+ }
-// Apply the key-value pair style to the table
-table.metrics {
- border-collapse: collapse;
- width: 100%;
- caption {
- font-size: 1.2em;
- font-weight: bold;
- padding-bottom: 10px;
- }
- thead {
- border: 1px solid $medium-grey;
- display: flex;
- flex-direction: column;
- width: fit-content;
- margin-bottom: 1rem;
-
- tr{
- display: contents;
- th{
- display: block;
- white-space: nowrap;
+ td.metric_type{
+ min-width: 7em;
+ }
+ td.metric_stability_level{
+ min-width: 6em;
}
}
- }
- tbody {
- tr.metric {
- td {
- @include key-value-pair;
- display: block;
- margin-bottom: 1rem;
- min-width: 2rem;
- }
- td.metric_name {
- font-weight: 700;
- }
- td.metric_labels_varying{
- div {
- position: relative;
- padding-left: 1em;
- &::before{
- content: '-';
- position: absolute;
- left:0;
+ tbody{ // Tested dimensions to improve overall aesthetic of the table
+ tr {
+ td {
+ font-size: smaller;
}
+ td.metric_labels_varying{
+ min-width: 9em;
}
+ td.metric_type{
+ min-width: 9em;
+ }
+ td.metric_description{
+ min-width: 10em;
+ }
+
}
}
- }
-}
table.no-word-break td,
table.no-word-break code {
word-break: normal;
- }
-
+}
}
// blockquotes and callouts
From 7e7571bb1900796785866d485009c7f921c08c49 Mon Sep 17 00:00:00 2001
From: Gauravpadam <1032201077@tcetmumbai.in>
Date: Sun, 6 Aug 2023 18:41:54 +0530
Subject: [PATCH 138/446] table.metrics selector added
---
assets/scss/_custom.scss | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/assets/scss/_custom.scss b/assets/scss/_custom.scss
index fa53a99a04..6f5a4c1f6d 100644
--- a/assets/scss/_custom.scss
+++ b/assets/scss/_custom.scss
@@ -358,6 +358,7 @@ main {
@media (max-width: 767px) { // for mobile devices, Display the names, Stability levels & types
+ table.metrics {
th:nth-child(n + 4),
td:nth-child(n + 4) {
display: none;
@@ -370,8 +371,9 @@ main {
min-width: 6em;
}
}
+ }
- tbody{ // Tested dimensions to improve overall aesthetic of the table
+ table.metrics tbody{ // Tested dimensions to improve overall aesthetic of the table
tr {
td {
font-size: smaller;
From 87c92444c5a5ef0828aebad8ea77046e86cf2bc8 Mon Sep 17 00:00:00 2001
From: "xin.li"
Date: Sun, 6 Aug 2023 22:55:47 +0800
Subject: [PATCH 139/446] [zh-cn] sync storage-classes.md storage-limits.md
volume-health-monitoring.md
Signed-off-by: xin.li
---
.../docs/concepts/storage/storage-classes.md | 71 +++++--------------
.../docs/concepts/storage/storage-limits.md | 20 +++---
.../storage/volume-health-monitoring.md | 9 +--
3 files changed, 31 insertions(+), 69 deletions(-)
diff --git a/content/zh-cn/docs/concepts/storage/storage-classes.md b/content/zh-cn/docs/concepts/storage/storage-classes.md
index cb023d47a7..44f0961022 100644
--- a/content/zh-cn/docs/concepts/storage/storage-classes.md
+++ b/content/zh-cn/docs/concepts/storage/storage-classes.md
@@ -38,9 +38,9 @@ systems.
-->
## 介绍 {#introduction}
-StorageClass 为管理员提供了描述存储 "类" 的方法。
+StorageClass 为管理员提供了描述存储"类"的方法。
不同的类型可能会映射到不同的服务质量等级或备份策略,或是由集群管理员制定的任意策略。
-Kubernetes 本身并不清楚各种类代表的什么。这个类的概念在其他存储系统中有时被称为 "配置文件"。
+Kubernetes 本身并不清楚各种类代表的什么。这个类的概念在其他存储系统中有时被称为"配置文件"。
StorageClass 对象的命名很重要,用户使用这个命名来请求生成一个特定的类。
-当创建 StorageClass 对象时,管理员设置 StorageClass 对象的命名和其他参数,一旦创建了对象就不能再对其更新。
+当创建 StorageClass 对象时,管理员设置 StorageClass 对象的命名和其他参数,
+一旦创建了对象就不能再对其更新。
-以下插件支持动态制备的 `WaitForFirstConsumer` 模式:
+以下插件支持动态制备的 `WaitForFirstConsumer` 模式:
-- [AWSElasticBlockStore](#aws-ebs)
- [GCEPersistentDisk](#gce-pd)
-- [AzureDisk](#azure-disk)
-- `type`:`io1`,`gp2`,`sc1`,`st1`。详细信息参见
+- `type`:`io1`、`gp2`、`sc1`、`st1`。详细信息参见
[AWS 文档](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html)。默认值:`gp2`。
-- `zone`(弃用):AWS 区域。如果没有指定 `zone` 和 `zones`,
+- `zone`(已弃用):AWS 区域。如果没有指定 `zone` 和 `zones`,
通常卷会在 Kubernetes 集群节点所在的活动区域中轮询调度分配。
`zone` 和 `zones` 参数不能同时使用。
-- `zones`(弃用):以逗号分隔的 AWS 区域列表。
+- `zones`(已弃用):以逗号分隔的 AWS 区域列表。
如果没有指定 `zone` 和 `zones`,通常卷会在 Kubernetes 集群节点所在的活动区域中轮询调度分配。
`zone`和`zones`参数不能同时使用。
- `iopsPerGB`:只适用于 `io1` 卷。每 GiB 每秒 I/O 操作。
@@ -484,7 +475,7 @@ parameters:
这里需要输入一个字符串,即 `"10"`,而不是 `10`。
- `fsType`:受 Kubernetes 支持的文件类型。默认值:`"ext4"`。
- `encrypted`:指定 EBS 卷是否应该被加密。合法值为 `"true"` 或者 `"false"`。
- 这里需要输入字符串,即 `"true"`, 而非 `true`。
+ 这里需要输入字符串,即 `"true"`,而非 `true`。
- `kmsKeyId`:可选。加密卷时使用密钥的完整 Amazon 资源名称。
如果没有提供,但 `encrypted` 值为 true,AWS 生成一个密钥。关于有效的 ARN 值,请参阅 AWS 文档。
@@ -524,13 +515,13 @@ parameters:
- `replication-type`: `none` or `regional-pd`. Default: `none`.
-->
- `type`:`pd-standard` 或者 `pd-ssd`。默认:`pd-standard`
-- `zone`(弃用):GCE 区域。如果没有指定 `zone` 和 `zones`,
+- `zone`(已弃用):GCE 区域。如果没有指定 `zone` 和 `zones`,
通常卷会在 Kubernetes 集群节点所在的活动区域中轮询调度分配。
`zone` 和 `zones` 参数不能同时使用。
-- `zones`(弃用):逗号分隔的 GCE 区域列表。如果没有指定 `zone` 和 `zones`,
+- `zones`(已弃用):逗号分隔的 GCE 区域列表。如果没有指定 `zone` 和 `zones`,
通常卷会在 Kubernetes 集群节点所在的活动区域中轮询调度(round-robin)分配。
`zone` 和 `zones` 参数不能同时使用。
-- `fstype`:`ext4` 或 `xfs`。 默认:`ext4`。宿主机操作系统必须支持所定义的文件系统类型。
+- `fstype`:`ext4` 或 `xfs`。默认:`ext4`。宿主机操作系统必须支持所定义的文件系统类型。
- `replication-type`:`none` 或者 `regional-pd`。默认值:`none`。
-- `availability`:可用区域。如果没有指定,通常卷会在 Kubernetes 集群节点所在的活动区域中轮转调度。
-
-{{< note >}}
-{{< feature-state state="deprecated" for_k8s_version="v1.11" >}}
-
-OpenStack 的内部驱动已经被弃用。请使用
-[OpenStack 的外部云驱动](https://github.com/kubernetes/cloud-provider-openstack)。
-{{< /note >}}
-
### vSphere {#vsphere}
#### vCP 制备器 {#vcp-provisioner}
-以下示例使用 VMware Cloud Provider (vCP) StorageClass 制备器。
+以下示例使用 VMware Cloud Provider(vCP)StorageClass 制备器。
谷歌、亚马逊和微软等云供应商通常对可以关联到节点的卷数量进行限制。
-Kubernetes 需要尊重这些限制。 否则,在节点上调度的 Pod 可能会卡住去等待卷的关联。
+Kubernetes 需要尊重这些限制。否则,在节点上调度的 Pod 可能会卡住去等待卷的关联。
@@ -108,7 +108,7 @@ Dynamic volume limits are supported for following volume types.
For volumes managed by in-tree volume plugins, Kubernetes automatically determines the Node
type and enforces the appropriate maximum number of volumes for the node. For example:
-->
-对于由内建插件管理的卷,Kubernetes 会自动确定节点类型并确保节点上可关联的卷数目合规。 例如:
+对于由内建插件管理的卷,Kubernetes 会自动确定节点类型并确保节点上可关联的卷数目合规。例如:
* 在
-Google Compute Engine环境中,
-[根据节点类型](https://cloud.google.com/compute/docs/disks/#pdnumberlimits)最多可以将127个卷关联到节点。
+ Google Compute Engine环境中,
+ [根据节点类型](https://cloud.google.com/compute/docs/disks/#pdnumberlimits)最多可以将 127 个卷关联到节点。
* 对于 M5、C5、R5、T3 和 Z1D 类型实例的 Amazon EBS 磁盘,Kubernetes 仅允许 25 个卷关联到节点。
-对于 ec2 上的其他实例类型
-Amazon Elastic Compute Cloud (EC2),
-Kubernetes 允许 39 个卷关联至节点。
+ 对于 ec2 上的其他实例类型
+ Amazon Elastic Compute Cloud (EC2),
+ Kubernetes 允许 39 个卷关联至节点。
* 在 Azure 环境中, 根据节点类型,最多 64 个磁盘可以关联至一个节点。
-更多详细信息,请参阅[Azure 虚拟机的数量大小](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes)。
+ 更多详细信息,请参阅 [Azure 虚拟机的数量大小](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes)。
* 如果 CSI 存储驱动程序(使用 `NodeGetInfo` )为节点通告卷数上限,则 {{< glossary_tooltip text="kube-scheduler" term_id="kube-scheduler" >}} 将遵守该限制值。
-参考 [CSI 规范](https://github.com/container-storage-interface/spec/blob/master/spec.md#nodegetinfo) 获取更多详细信息。
+ 参考 [CSI 规范](https://github.com/container-storage-interface/spec/blob/master/spec.md#nodegetinfo) 获取更多详细信息。
* 对于由已迁移到 CSI 驱动程序的树内插件管理的卷,最大卷数将是 CSI 驱动程序报告的卷数。
-
-
diff --git a/content/zh-cn/docs/concepts/storage/volume-health-monitoring.md b/content/zh-cn/docs/concepts/storage/volume-health-monitoring.md
index 0c8da44608..6359ff0e94 100644
--- a/content/zh-cn/docs/concepts/storage/volume-health-monitoring.md
+++ b/content/zh-cn/docs/concepts/storage/volume-health-monitoring.md
@@ -25,8 +25,8 @@ and report them as events on {{< glossary_tooltip text="PVCs" term_id="persisten
or {{< glossary_tooltip text="Pods" term_id="pod" >}}.
-->
{{< glossary_tooltip text="CSI" term_id="csi" >}} 卷健康监测支持 CSI 驱动从底层的存储系统着手,
-探测异常的卷状态,并以事件的形式上报到 {{< glossary_tooltip text="PVCs" term_id="persistent-volume-claim" >}}
-或 {{< glossary_tooltip text="Pods" term_id="pod" >}}.
+探测异常的卷状态,并以事件的形式上报到 {{< glossary_tooltip text="PVC" term_id="persistent-volume-claim" >}}
+或 {{< glossary_tooltip text="Pod" term_id="pod" >}}.
@@ -46,7 +46,7 @@ an event will be reported on the related
{{< glossary_tooltip text="PersistentVolumeClaim" term_id="persistent-volume-claim" >}} (PVC)
when an abnormal volume condition is detected on a CSI volume.
-->
-Kubernetes _卷健康监测_ 是 Kubernetes 容器存储接口(CSI)实现的一部分。
+Kubernetes **卷健康监测**是 Kubernetes 容器存储接口(CSI)实现的一部分。
卷健康监测特性由两个组件实现:外部健康监测控制器和 {{< glossary_tooltip term_id="kubelet" text="kubelet" >}}。
如果 CSI 驱动器通过控制器的方式支持卷健康监测特性,那么只要在 CSI 卷上监测到异常卷状态,就会在
@@ -79,7 +79,8 @@ is healthy. For more information, please check
此外,卷运行状况信息作为 Kubelet VolumeStats 指标公开。
添加了一个新的指标 kubelet_volume_stats_health_status_abnormal。
该指标包括两个标签:`namespace` 和 `persistentvolumeclaim`。
-计数为 1 或 0。1 表示卷不正常,0 表示卷正常。更多信息请访问[KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1432-volume-health-monitor#kubelet-metrics-changes)。
+计数为 1 或 0。1 表示卷不正常,0 表示卷正常。更多信息请访问
+[KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1432-volume-health-monitor#kubelet-metrics-changes)。
下面包含的清单文件指定了一个 Deployment 控制器,该控制器运行一个 Redis Pod 副本。
-{{< codenew file="application/guestbook/redis-leader-deployment.yaml" >}}
+{{< code file="application/guestbook/redis-leader-deployment.yaml" >}}
### 创建 Guestbook 前端 Deployment {#creating-the-guestbook-frontend-deployment}
-{{< codenew file="application/guestbook/frontend-deployment.yaml" >}}
+{{< code file="application/guestbook/frontend-deployment.yaml" >}}
-你可以使用 `{{* codenew */>}}` 短代码将文件内容嵌入代码块中,
+## 源代码文件
+你可以使用 `{{* code */>}}` 短代码将文件内容嵌入代码块中,
以允许用户下载或复制其内容到他们的剪贴板。
当示例文件的内容是通用的、可复用的,并且希望用户自己尝试使用示例文件时,
可以使用此短代码。
@@ -475,7 +476,7 @@ For example:
如果未提供 `language` 参数,短代码将尝试根据文件扩展名推测编程语言。
```none
-{{* codenew language="yaml" file="application/deployment-scale.yaml" */>}}
+{{* code language="yaml" file="application/deployment-scale.yaml" */>}}
```
输出是:
-{{< codenew language="yaml" file="application/deployment-scale.yaml" >}}
+{{< code language="yaml" file="application/deployment-scale.yaml" >}}
添加新的示例文件(例如 YAML 文件)时,在 `/examples/`
子目录之一中创建该文件,其中 `` 是页面的语言。
-在你的页面的 markdown 文本中,使用 `codenew` 短代码:
+在你的页面的 markdown 文本中,使用 `code` 短代码:
```none
-{{* codenew file="/example-yaml>" */>}}
+{{* code file="/example-yaml>" */>}}
```
其中 `` 是要包含的示例文件的路径,相对于 `examples` 目录。
以下短代码引用位于 `/content/en/examples/configmap/configmaps.yaml` 的 YAML 文件。
```none
-{{* codenew file="configmap/configmaps.yaml" */>}}
+{{* code file="configmap/configmaps.yaml" */>}}
```
+
+传统的 `{{%/* codenew */%}}` 短代码将被替换为 `{{%/* code */%}}`。
+在新文档中使用 `{{%/* code */%}}`。
+
From 3a5deff8c47f4b4e1e22325db8516233226bc875 Mon Sep 17 00:00:00 2001
From: bzsuni
Date: Mon, 7 Aug 2023 16:50:04 +0800
Subject: [PATCH 169/446] sync
blog/_posts/2023-05-15-kubernetes-1-27-updates-on-speeding-up-pod-startup.md
Signed-off-by: bzsuni
---
...-kubernetes-1-27-updates-on-speeding-up-pod-startup.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/zh-cn/blog/_posts/2023-05-15-kubernetes-1-27-updates-on-speeding-up-pod-startup.md b/content/zh-cn/blog/_posts/2023-05-15-kubernetes-1-27-updates-on-speeding-up-pod-startup.md
index b617c0c576..d72b09ab6a 100644
--- a/content/zh-cn/blog/_posts/2023-05-15-kubernetes-1-27-updates-on-speeding-up-pod-startup.md
+++ b/content/zh-cn/blog/_posts/2023-05-15-kubernetes-1-27-updates-on-speeding-up-pod-startup.md
@@ -140,7 +140,7 @@ More detials can be found in the KEP and the pull requ
## Event triggered updates to container status
`Evented PLEG` (PLEG is short for "Pod Lifecycle Event Generator") is set to be in beta for v1.27,
-Kubernetes offers two ways for the kubelet to detect Pod lifecycle events, such as a the last
+Kubernetes offers two ways for the kubelet to detect Pod lifecycle events, such as the last
process in a container shutting down.
In Kubernetes v1.27, the _event based_ mechanism has graduated to beta but remains
disabled by default. If you do explicitly switch to event-based lifecycle change detection,
@@ -190,7 +190,7 @@ CGroup V2 时的内存质量。尽管此特性门控有一定的好处,但如
Kubelet 配置现在包括 `memoryThrottlingFactor`。该因子乘以内存限制或节点可分配内存,
-可以设置 cgroupv2 memory.high 值来执行 MemoryQoS。
+可以设置 cgroupv2 `memory.high` 值来执行 MemoryQoS。
减小该因子将为容器 cgroup 设置较低的上限,同时增加了回收压力。
提高此因子将减少回收压力。默认值最初为 0.8,并将在 Kubernetes v1.27 中更改为 0.9。
调整此参数可以减少此特性对 Pod 启动速度的潜在影响。
@@ -226,7 +226,7 @@ container startup by mounting volumes with the correct SELinux label instead of
on the volumes recursively. Further details can be found in the KEP .
To identify the cause of slow pod startup, analyzing metrics and logs can be helpful. Other
-factorsthat may impact pod startup include container runtime, disk speed, CPU and memory
+factors that may impact pod startup include container runtime, disk speed, CPU and memory
resources on the node.
-->
SELinux 挂载选项重标记功能在 v1.27 中升至 Beta 版本。
From 6ae1678418550aa2993cd4cc9c2047aebc332c28 Mon Sep 17 00:00:00 2001
From: bzsuni
Date: Mon, 7 Aug 2023 17:03:58 +0800
Subject: [PATCH 170/446] sync concepts/configuration/configmap.md
Signed-off-by: bzsuni
---
content/zh-cn/docs/concepts/configuration/configmap.md | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/content/zh-cn/docs/concepts/configuration/configmap.md b/content/zh-cn/docs/concepts/configuration/configmap.md
index 9cc4cffaf7..7d4a187372 100644
--- a/content/zh-cn/docs/concepts/configuration/configmap.md
+++ b/content/zh-cn/docs/concepts/configuration/configmap.md
@@ -189,7 +189,7 @@ Here's an example Pod that uses values from `game-demo` to configure a Pod:
下面是一个 Pod 的示例,它通过使用 `game-demo` 中的值来配置一个 Pod:
-{{< codenew file="configmap/configure-pod.yaml" >}}
+{{% code file="configmap/configure-pod.yaml" %}}
-此功能特性由 `ImmutableEphemeralVolumes`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来控制。
你可以通过将 `immutable` 字段设置为 `true` 创建不可变更的 ConfigMap。
例如:
From 8845106eecd3a9e18631a97afcae47918ff78d42 Mon Sep 17 00:00:00 2001
From: bzsuni
Date: Mon, 7 Aug 2023 17:12:14 +0800
Subject: [PATCH 171/446] sync concepts/overview/working-with-objects/_index.md
Signed-off-by: bzsuni
---
.../zh-cn/docs/concepts/overview/working-with-objects/_index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/zh-cn/docs/concepts/overview/working-with-objects/_index.md b/content/zh-cn/docs/concepts/overview/working-with-objects/_index.md
index c612d8bfb3..dccc90d015 100644
--- a/content/zh-cn/docs/concepts/overview/working-with-objects/_index.md
+++ b/content/zh-cn/docs/concepts/overview/working-with-objects/_index.md
@@ -157,7 +157,7 @@ Here's an example `.yaml` file that shows the required fields and object spec fo
-->
这里有一个 `.yaml` 示例文件,展示了 Kubernetes Deployment 的必需字段和对象 `spec`:
-{{< codenew file="application/deployment.yaml" >}}
+{{< code file="application/deployment.yaml" >}}
以及一个声明 CPU 资源请求为 `700m` 但未声明限制值的 Pod:
-{{< codenew file="concepts/policy/limit-range/example-conflict-with-limitrange-cpu.yaml" >}}
+{{% code file="concepts/policy/limit-range/example-conflict-with-limitrange-cpu.yaml" %}}
如果你同时设置了 `request` 和 `limit`,那么即使使用相同的 `LimitRange`,新 Pod 也会被成功调度:
-{{< codenew file="concepts/policy/limit-range/example-no-conflict-with-limitrange-cpu.yaml" >}}
+{{% code file="concepts/policy/limit-range/example-no-conflict-with-limitrange-cpu.yaml" %}}
以下是具有自定义 DNS 设置的 Pod 示例:
-{{< codenew file="service/networking/custom-dns.yaml" >}}
+{{% code file="service/networking/custom-dns.yaml" %}}
这将需要一个如下所示的 Ingress:
-{{< codenew file="service/networking/simple-fanout-example.yaml" >}}
+{{% code file="service/networking/simple-fanout-example.yaml" %}}
+
+
+**作者:** Xing Yang (VMware) and Ashutosh Kumar (Elastic)
+
+**译者:** Xin Li (Daocloud)
+
+
+Kubernetes 节点非体面关闭特性现已在 Kubernetes v1.28 中正式发布。
+
+此特性在 Kubernetes v1.24 中作为 [Alpha](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2268-non-graceful-shutdown)
+特性引入,并在 Kubernetes v1.26 中转入 [Beta](https://kubernetes.io/blog/2022/12/16/kubernetes-1-26-non-graceful-node-shutdown-beta/)
+阶段。如果原始节点意外关闭或最终处于不可恢复状态(例如硬件故障或操作系统无响应),
+此特性允许有状态工作负载在不同节点上重新启动。
+
+
+## 什么是节点非体面关闭
+
+在 Kubernetes 集群中,节点可能会按计划正常关闭,也可能由于断电或其他外部原因而意外关闭。
+如果节点在关闭之前未腾空,则节点关闭可能会导致工作负载失败。节点关闭可以是正常关闭,也可以是非正常关闭。
+
+
+[节点体面关闭](https://kubernetes.io/blog/2021/04/21/graceful-node-shutdown-beta/)特性允许
+kubelet 在实际关闭之前检测节点关闭事件、正确终止该节点上的 Pod 并释放资源。
+
+
+当节点关闭但 kubelet 的节点关闭管理器未检测到时,将造成节点非体面关闭。
+对于无状态应用程序来说,节点非体面关闭通常不是问题,但是对于有状态应用程序来说,这是一个问题。
+如果 Pod 停留在关闭节点上并且未在正在运行的节点上重新启动,则有状态应用程序将无法正常运行。
+
+
+在节点非体面关闭的情况下,你可以在 Node 上手动添加 `out-of-service` 污点。
+
+```
+kubectl taint nodes node.kubernetes.io/out-of-service=nodeshutdown:NoExecute
+```
+
+
+如果 Pod 上没有与之匹配的容忍规则,则此污点会触发节点上的 Pod 被强制删除。
+挂接到关闭中的节点的持久卷将被解除挂接,新的 Pod 将在不同的运行节点上成功创建。
+
+
+**注意:**在应用 out-of-service 污点之前,你必须验证节点是否已经处于关闭或断电状态(而不是在重新启动中)。
+
+与 out-of-service 节点有关联的所有工作负载的 Pod 都被移动到新的运行节点,
+并且所关闭的节点已恢复之后,你应该删除受影响节点上的污点。
+
+
+## 稳定版中有哪些新内容
+
+随着非正常节点关闭功能提升到稳定状态,特性门控
+`NodeOutOfServiceVolumeDetach` 在 `kube-controller-manager` 上被锁定为 true,并且无法禁用。
+
+
+Pod GC 控制器中的指标 `force_delete_pods_total` 和 `force_delete_pod_errors_total`
+得到增强,以考虑所有 Pod 的强制删除情况。
+指标中会添加一个 "reason",以指示 Pod 是否因终止、孤儿、因 `out-of-service`
+污点而终止或因未计划终止而被强制删除。
+
+
+Attach Detach Controller 中的指标 `attachdetach_controller_forced_detaches`
+中还会添加一个 "reason",以指示强制解除挂接是由 `out-of-service` 污点还是超时引起的。
+
+
+## 接下来
+
+此特性要求用户手动向节点添加污点以触发工作负载故障转移,并在节点恢复后删除污点。
+未来,我们计划找到方法来自动检测和隔离关闭/失败的节点,并自动将工作负载故障转移到另一个节点。
+
+
+## 如何了解更多?
+
+在[此处](/zh-cn/docs/concepts/architecture/nodes/#non-graceful-node-shutdown)可以查看有关此特性的其他文档。
+
+
+我们非常感谢所有帮助设计、实现和审查此功能并帮助其从 Alpha、Beta 到稳定版的贡献者:
+
+* Michelle Au ([msau42](https://github.com/msau42))
+* Derek Carr ([derekwaynecarr](https://github.com/derekwaynecarr))
+* Danielle Endocrimes ([endocrimes](https://github.com/endocrimes))
+* Baofa Fan ([carlory](https://github.com/carlory))
+* Tim Hockin ([thockin](https://github.com/thockin))
+* Ashutosh Kumar ([sonasingh46](https://github.com/sonasingh46))
+* Hemant Kumar ([gnufied](https://github.com/gnufied))
+* Yuiko Mouri ([YuikoTakada](https://github.com/YuikoTakada))
+* Mrunal Patel ([mrunalp](https://github.com/mrunalp))
+* David Porter ([bobbypage](https://github.com/bobbypage))
+* Yassine Tijani ([yastij](https://github.com/yastij))
+* Jing Xu ([jingxu97](https://github.com/jingxu97))
+* Xing Yang ([xing-yang](https://github.com/xing-yang))
+
+
+此特性是 SIG Storage 和 SIG Node 之间的协作。对于那些有兴趣参与 Kubernetes
+存储系统任何部分的设计和开发的人,请加入 Kubernetes 存储特别兴趣小组(SIG)。
+对于那些有兴趣参与支持 Pod 和主机资源之间受控交互的组件的设计和开发,请加入 Kubernetes Node SIG。
From 73d698edf1bd4ba2e4faf695811365e229d14f6e Mon Sep 17 00:00:00 2001
From: Rodrigo Campos
Date: Thu, 6 Jul 2023 11:43:35 +0200
Subject: [PATCH 178/446] content: Fix typos in versions requirements for
userns
The variable expansion is wrong: it currently expands to 1.27.3 on the
rendered website, so it says it is supported in 1.27 and that it is not.
Let's just re-work this paragraph so it is cleaerer and the variable
expansion is what we want (1.27 and not 1.27.3)-
Signed-off-by: Rodrigo Campos
---
.../en/docs/concepts/workloads/pods/user-namespaces.md | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/concepts/workloads/pods/user-namespaces.md b/content/en/docs/concepts/workloads/pods/user-namespaces.md
index 623337dbd3..cb0452d474 100644
--- a/content/en/docs/concepts/workloads/pods/user-namespaces.md
+++ b/content/en/docs/concepts/workloads/pods/user-namespaces.md
@@ -54,9 +54,13 @@ to use this feature with Kubernetes stateless pods:
* CRI-O: version 1.25 (and later) supports user namespaces for containers.
-Please note that containerd v1.7 supports user namespaces for containers,
-compatible with Kubernetes {{< skew currentPatchVersion >}}. It should not be used
-with Kubernetes 1.27 (and later).
+containerd v1.7 is not compatible with the userns support in Kubernetes v{{< skew currentVersion >}}.
+Kubernetes v1.25 and v1.26 used an earlier implementation that **is** compatible with containerd v1.7,
+in terms of userns support.
+If you are using a version of Kubernetes other than {{< skew currentVersion >}},
+check the documentation for that version of Kubernetes for the most relevant information.
+If there is a newer release of containerd than v1.7 available for use, also check the containerd
+documentation for compatibility information.
Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.
From 5e70c9a88a44b6c02495dce9a6a31e846cd550a2 Mon Sep 17 00:00:00 2001
From: Rodrigo Campos
Date: Fri, 7 Jul 2023 12:17:10 +0200
Subject: [PATCH 179/446] content: Remove old note about userns
The note is no longer valid (the branch was already merged and the
merged was done correctly).
Signed-off-by: Rodrigo Campos
---
content/en/docs/concepts/workloads/pods/user-namespaces.md | 2 --
1 file changed, 2 deletions(-)
diff --git a/content/en/docs/concepts/workloads/pods/user-namespaces.md b/content/en/docs/concepts/workloads/pods/user-namespaces.md
index cb0452d474..f2d81f3ed5 100644
--- a/content/en/docs/concepts/workloads/pods/user-namespaces.md
+++ b/content/en/docs/concepts/workloads/pods/user-namespaces.md
@@ -46,8 +46,6 @@ 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:
From 922458da9a55d27667a33eb249240284507a6a16 Mon Sep 17 00:00:00 2001
From: Rodrigo Campos
Date: Fri, 7 Jul 2023 12:37:46 +0200
Subject: [PATCH 180/446] content: Make userns statement about dockerd timeless
Signed-off-by: Rodrigo Campos
---
content/en/docs/concepts/workloads/pods/user-namespaces.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/workloads/pods/user-namespaces.md b/content/en/docs/concepts/workloads/pods/user-namespaces.md
index f2d81f3ed5..408abb6d16 100644
--- a/content/en/docs/concepts/workloads/pods/user-namespaces.md
+++ b/content/en/docs/concepts/workloads/pods/user-namespaces.md
@@ -60,7 +60,8 @@ check the documentation for that version of Kubernetes for the most relevant inf
If there is a newer release of containerd than v1.7 available for use, also check the containerd
documentation for compatibility information.
-Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.
+You can see the status of user namespaces support in cri-dockerd tracked in an [issue][CRI-dockerd-issue]
+on GitHub.
[CRI-dockerd-issue]: https://github.com/Mirantis/cri-dockerd/issues/74
From 3c888c82e70ae2a8b2873b9ebaf20406cc2eef28 Mon Sep 17 00:00:00 2001
From: "xin.li"
Date: Mon, 7 Aug 2023 22:39:40 +0800
Subject: [PATCH 181/446] [zh-cn]sync assign-pods-nodes configure-runasusername
extended-resource
Signed-off-by: xin.li
---
.../docs/tasks/configure-pod-container/assign-pods-nodes.md | 4 ++--
.../tasks/configure-pod-container/configure-runasusername.md | 4 ++--
.../docs/tasks/configure-pod-container/extended-resource.md | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/zh-cn/docs/tasks/configure-pod-container/assign-pods-nodes.md b/content/zh-cn/docs/tasks/configure-pod-container/assign-pods-nodes.md
index 98dffd4d14..2ed27fc9b4 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/assign-pods-nodes.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/assign-pods-nodes.md
@@ -100,7 +100,7 @@ a `disktype=ssd` label.
此 Pod 配置文件描述了一个拥有节点选择器 `disktype: ssd` 的 Pod。这表明该 Pod
将被调度到有 `disktype=ssd` 标签的节点。
-{{< codenew file="pods/pod-nginx.yaml" >}}
+{{% codenew file="pods/pod-nginx.yaml" %}}
{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
-This page shows how to configure a user namespace for stateless pods. This
-allows to isolate the user running inside the container from the one in the
-host.
+This page shows how to configure a user namespace for pods. This allows to
+isolate the user running inside the container from the one in the host.
A process running as root in a container can run as a different (non-root) user
in the host; in other words, the process has full privileges for operations
@@ -41,7 +40,14 @@ this is true when user namespaces are used.
* The node OS needs to be Linux
* You need to exec commands in the host
* You need to be able to exec into pods
-* Feature gate `UserNamespacesStatelessPodsSupport` need to be enabled.
+* You need to enable the `UserNamespacesSupport`
+ [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+
+{{< note >}}
+The feature gate to enable user namespaces was previously named
+`UserNamespacesStatelessPodsSupport`, when only stateless pods were supported.
+Only Kubernetes v1.25 through to v1.27 recognise `UserNamespacesStatelessPodsSupport`.
+{{ note >}}
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)
@@ -59,8 +65,8 @@ created without user namespaces.**
## Run a Pod that uses a user namespace {#create-pod}
-A user namespace for a stateless pod is enabled setting the `hostUsers` field of
-`.spec` to `false`. For example:
+A user namespace for a pod is enabled setting the `hostUsers` field of `.spec`
+to `false`. For example:
{{< codenew file="pods/user-namespaces-stateless.yaml" >}}
From 6c2a9c574cde5d6077e2e48627acc6793d91206a Mon Sep 17 00:00:00 2001
From: Rodrigo Campos
Date: Mon, 7 Aug 2023 15:48:33 +0200
Subject: [PATCH 183/446] content: Expand version requirements for userns
explanation
---
content/en/docs/concepts/workloads/pods/user-namespaces.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/workloads/pods/user-namespaces.md b/content/en/docs/concepts/workloads/pods/user-namespaces.md
index 129de072cc..fa51a47d30 100644
--- a/content/en/docs/concepts/workloads/pods/user-namespaces.md
+++ b/content/en/docs/concepts/workloads/pods/user-namespaces.md
@@ -52,7 +52,7 @@ to use this feature with Kubernetes pods:
* CRI-O: version 1.25 (and later) supports user namespaces for containers.
-containerd v1.7 is not compatible with the userns support in Kubernetes v{{< skew currentVersion >}}.
+containerd v1.7 is not compatible with the userns support in Kubernetes v1.27 to v{{< skew latestVersion >}}.
Kubernetes v1.25 and v1.26 used an earlier implementation that **is** compatible with containerd v1.7,
in terms of userns support.
If you are using a version of Kubernetes other than {{< skew currentVersion >}},
From c250efb81acf1da71d8c2b180add618a9d8c9cf4 Mon Sep 17 00:00:00 2001
From: Rodrigo Campos
Date: Mon, 7 Aug 2023 15:50:03 +0200
Subject: [PATCH 184/446] content: Fix typo
Signed-off-by: Rodrigo Campos
---
.../en/docs/tasks/configure-pod-container/user-namespaces.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 27f5828cbb..e28a4038a9 100644
--- a/content/en/docs/tasks/configure-pod-container/user-namespaces.md
+++ b/content/en/docs/tasks/configure-pod-container/user-namespaces.md
@@ -9,7 +9,7 @@ min-kubernetes-server-version: v1.25
{{< feature-state for_k8s_version="v1.25" state="alpha" >}}
-This page shows how to configure a user namespace for pods. This allows to
+This page shows how to configure a user namespace for pods. This allows you to
isolate the user running inside the container from the one in the host.
A process running as root in a container can run as a different (non-root) user
From 271f86e30ef5e85ffe96a3a383dec452a0f951be Mon Sep 17 00:00:00 2001
From: Rishit Dagli
Date: Mon, 7 Aug 2023 12:09:47 -0400
Subject: [PATCH 185/446] Update data/releases/schedule.yaml
Co-authored-by: Tim Bannister
---
data/releases/schedule.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index 80c10aa266..6738ad9b47 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -4,7 +4,8 @@
schedules:
- release: 1.28
releaseDate: 2023-08-15
- next: 1.28.1
+ next:
+ release: 1.28.1
cherryPickDeadline: 2023-09-08
targetDate: 2023-09-13
endOfLifeDate: 2024-10-28
From a8ba9b848d089253b234643ef2837cd2b6e36bd8 Mon Sep 17 00:00:00 2001
From: Rishit Dagli
Date: Mon, 7 Aug 2023 12:10:24 -0400
Subject: [PATCH 186/446] Update data/releases/schedule.yaml
Co-authored-by: Tim Bannister
---
data/releases/schedule.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index 6738ad9b47..a6523678a0 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -9,6 +9,9 @@ schedules:
cherryPickDeadline: 2023-09-08
targetDate: 2023-09-13
endOfLifeDate: 2024-10-28
+ previousPatches:
+ - release: 1.28.0
+ targetDate: 2023-08-15
- release: 1.27
releaseDate: 2024-04-11
maintenanceModeStartDate: 2024-04-28
From acb09b983502fd7c1739c95213b795d1c9e0c3ba Mon Sep 17 00:00:00 2001
From: Rakshit Sharma
Date: Mon, 7 Aug 2023 21:33:23 +0530
Subject: [PATCH 187/446] Corrected typos in docs
---
content/en/docs/concepts/storage/volumes.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index da0e60050c..2948620fd0 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -1061,7 +1061,7 @@ persistent volume:
`ControllerPublishVolume` and `ControllerUnpublishVolume` calls. This field is
optional, and may be empty if no secret is required. If the Secret
contains more than one secret, all secrets are passed.
-`nodeExpandSecretRef`: A reference to the secret containing sensitive
+* `nodeExpandSecretRef`: A reference to the secret containing sensitive
information to pass to the CSI driver to complete the CSI
`NodeExpandVolume` call. This field is optional, and may be empty if no
secret is required. If the object contains more than one secret, all
@@ -1116,8 +1116,8 @@ For more information on how to develop a CSI driver, refer to the
CSI node plugins need to perform various privileged
operations like scanning of disk devices and mounting of file systems. These operations
-differ for each host operating system. For Linux worker nodes, containerized CSI node
-node plugins are typically deployed as privileged containers. For Windows worker nodes,
+differ for each host operating system. For Linux worker nodes, containerized CSI node
+plugins are typically deployed as privileged containers. For Windows worker nodes,
privileged operations for containerized CSI node plugins is supported using
[csi-proxy](https://github.com/kubernetes-csi/csi-proxy), a community-managed,
stand-alone binary that needs to be pre-installed on each Windows node.
From 9369ca3317cb11718ca7529d0cbae4b5535ae23e Mon Sep 17 00:00:00 2001
From: Rolfe Dlugy-Hegwer
Date: Mon, 7 Aug 2023 13:10:03 -0400
Subject: [PATCH 188/446] [zh-cn] Replace deprecated fullversion shortcode
#41484
---
.../tasks/tools/install-kubectl-windows.md | 28 +++++++++----------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md b/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md
index ef83219190..6bdfa8c25a 100644
--- a/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md
+++ b/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md
@@ -42,7 +42,7 @@ The following methods exist for installing kubectl on Windows:
在 Windows 系统中安装 kubectl 有如下几种方法:
-
@@ -55,7 +55,7 @@ The following methods exist for installing kubectl on Windows:
### 用 curl 在 Windows 上安装 kubectl {#install-kubectl-binary-with-curl-on-windows}
2. 验证该可执行文件(可选步骤)
-
+
下载 `kubectl` 校验和文件:
```powershell
@@ -120,7 +120,7 @@ The following methods exist for installing kubectl on Windows:
$(Get-FileHash -Algorithm SHA256 .\kubectl.exe).Hash -eq $(Get-Content .\kubectl.exe.sha256)
```
-
2. 测试一下,确保安装的是最新版本:
@@ -213,7 +213,7 @@ installer or remove the Docker Desktop's `kubectl`.
kubectl version --client
```
-
3. 导航到你的 home 目录:
@@ -223,7 +223,7 @@ installer or remove the Docker Desktop's `kubectl`.
cd ~
```
-
4. 创建目录 `.kube`:
@@ -241,7 +241,7 @@ installer or remove the Docker Desktop's `kubectl`.
cd .kube
```
-
6. 配置 kubectl,以接入远程的 Kubernetes 集群:
@@ -251,20 +251,20 @@ installer or remove the Docker Desktop's `kubectl`.
```
{{< note >}}
-
编辑配置文件,你需要先选择一个文本编辑器,比如 Notepad。
{{< /note >}}
-
## 验证 kubectl 配置 {#verify-kubectl-configration}
{{< include "included/verify-kubectl.md" >}}
-
- 用提示的命令对 `CertUtil` 的输出和下载的校验和文件进行手动比较。
-
+
```cmd
CertUtil -hashfile kubectl-convert.exe SHA256
type kubectl-convert.exe.sha256
@@ -336,7 +336,7 @@ kubectl 为 Bash、Zsh、Fish 和 PowerShell 提供自动补全功能,可以
-->
- 使用 PowerShell `-eq` 操作使验证自动化,获得 `True` 或者 `False` 的结果:
-
+
```powershell
$($(CertUtil -hashfile .\kubectl-convert.exe SHA256)[1] -replace " ", "") -eq $(type .\kubectl-convert.exe.sha256)
```
From 29178c6a3ba463e2aefa38af4e1d00e7a676ec14 Mon Sep 17 00:00:00 2001
From: Karthik P M <72903849+Karthik-PM@users.noreply.github.com>
Date: Mon, 7 Aug 2023 22:54:38 +0530
Subject: [PATCH 189/446] Update style-guide.md
---
content/en/docs/contribute/style/style-guide.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/contribute/style/style-guide.md b/content/en/docs/contribute/style/style-guide.md
index 5972409087..63c87dc25f 100644
--- a/content/en/docs/contribute/style/style-guide.md
+++ b/content/en/docs/contribute/style/style-guide.md
@@ -651,7 +651,7 @@ You can remove ... | You can easily remove ...
These steps ... | These simple steps ...
{{< /table >}}
-### EditorConfig
+### EditorConfig file
The Kubernetes project maintains an EditorConfig file that sets common style preferences in text editors
such as VS Code. You can use this file if you want to ensure that your contributions are consistent with
the rest of the project. To view the file, refer to
From c00f6c397c74e733758f734e3009858e11f304b1 Mon Sep 17 00:00:00 2001
From: Arhell
Date: Tue, 8 Aug 2023 00:10:00 +0300
Subject: [PATCH 190/446] [id] attached correct link
---
content/id/docs/concepts/security/overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/id/docs/concepts/security/overview.md b/content/id/docs/concepts/security/overview.md
index 5fa480809c..30dfa12737 100644
--- a/content/id/docs/concepts/security/overview.md
+++ b/content/id/docs/concepts/security/overview.md
@@ -34,7 +34,7 @@ IaaS Provider | Link |
Alibaba Cloud | https://www.alibabacloud.com/trust-center |
Amazon Web Services | https://aws.amazon.com/security/ |
Google Cloud Platform | https://cloud.google.com/security/ |
-Huawei Cloud | https://www.huaweicloud.com/securecenter/overallsafety.html |
+Huawei Cloud | https://www.huaweicloud.com/intl/id-id/securecenter/overallsafety |
IBM Cloud | https://www.ibm.com/cloud/security |
Microsoft Azure | https://docs.microsoft.com/en-us/azure/security/azure-security |
Oracle Cloud Infrastructure | https://www.oracle.com/security/ |
From 9f81969201af11132f8773b1b63746eabd949e72 Mon Sep 17 00:00:00 2001
From: pegasas <616672335@qq.com>
Date: Sat, 29 Jul 2023 10:02:28 +0800
Subject: [PATCH 191/446] Remove NamespaceDefaultLabelName feature gate from
the Network Policies page
---
.../docs/concepts/services-networking/network-policies.md | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/content/en/docs/concepts/services-networking/network-policies.md b/content/en/docs/concepts/services-networking/network-policies.md
index 6dacf58ba5..1d0bfcb67a 100644
--- a/content/en/docs/concepts/services-networking/network-policies.md
+++ b/content/en/docs/concepts/services-networking/network-policies.md
@@ -340,12 +340,8 @@ namespaces based on their labels.
## Targeting a Namespace by its name
-{{< feature-state for_k8s_version="1.22" state="stable" >}}
-
The Kubernetes control plane sets an immutable label `kubernetes.io/metadata.name` on all
-namespaces, provided that the `NamespaceDefaultLabelName`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled.
-The value of the label is the namespace name.
+namespaces, the value of the label is the namespace name.
While NetworkPolicy cannot target a namespace by its name with some object field, you can use the
standardized label to target a specific namespace.
From e894028da7b101c3e4cef0ebafd8ff2dabddce77 Mon Sep 17 00:00:00 2001
From: Alexander Zielenski <351783+alexzielenski@users.noreply.github.com>
Date: Mon, 7 Aug 2023 22:10:04 -0700
Subject: [PATCH 192/446] move to other pages, add links
---
.../api-extension/custom-resources.md | 2 +-
.../feature-gates.md | 11 +----
.../custom-resource-definitions.md | 44 +++++++++++++++++++
3 files changed, 46 insertions(+), 11 deletions(-)
diff --git a/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md b/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md
index 2907d2f0fd..aafb04fd83 100644
--- a/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md
+++ b/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md
@@ -209,7 +209,7 @@ Aggregated APIs offer more advanced API features and customization of other feat
| Feature | Description | CRDs | Aggregated API |
| ------- | ----------- | ---- | -------------- |
-| Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes. Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation). Any other validations supported by addition of a [Validating Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook-alpha-in-1-8-beta-in-1-9). | Yes, arbitrary validation checks |
+| Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes. Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation). [CRDValidationRatcheting](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation-ratcheting) feature gate allows failing validations specified using OpenAPI also can be ignored if the failing part of the resource was unchanged. Any other validations supported by addition of a [Validating Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook-alpha-in-1-8-beta-in-1-9). | Yes, arbitrary validation checks |
| Defaulting | See above | Yes, either via [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#defaulting) `default` keyword (GA in 1.17), or via a [Mutating Webhook](/docs/reference/access-authn-authz/admission-controllers/#mutatingadmissionwebhook) (though this will not be run when reading from etcd for old objects). | Yes |
| Multi-versioning | Allows serving the same object through two API versions. Can help ease API changes like renaming fields. Less important if you control your client versions. | [Yes](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning) | Yes |
| Custom Storage | If you need storage with a different performance mode (for example, a time-series database instead of key-value store) or isolation for security (for example, encryption of sensitive information, etc.) | No | Yes |
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 18a74a2481..9734760236 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
@@ -460,16 +460,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
- `CronJobTimeZone`: Allow the use of the `timeZone` optional field in [CronJobs](/docs/concepts/workloads/controllers/cron-jobs/)
- `CRDValidationRatcheting`: Enable updates to custom resources to contain
violations of their OpenAPI schema if the offending portions of the resource
- update did not change. Allows users to update to stricter versions of a CRD
- schema without bumping the version of the object or breaking workflows.
- While most are supported, does not support ratcheting updates across all
- schema changes. The following OpenAPIV3 schema validations are not supported
- by ratcheting under the current implementation and if violated will continue
- to throw an error as normally:
- - `allOf`/`oneOf`/`anyOf`/`not` nested validations
- - `x-kubernetes-validations`
- - `x-kubernetes-list-type`
- - `required` fields
+ update did not change. See [Validation Ratcheting](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation-ratcheting) for more details.
- `CrossNamespaceVolumeDataSource`: Enable the usage of cross namespace volume data source
to allow you to specify a source namespace in the `dataSourceRef` field of a
PersistentVolumeClaim.
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 edade8f825..b3278af65c 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
@@ -717,6 +717,50 @@ And create it:
kubectl apply -f my-crontab.yaml
crontab "my-new-cron-object" created
```
+### Validation Ratcheting
+
+Validation Ratcheting is alpha since 1.28. Enable the `CRDValidationRatcheting`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to
+use the feature.
+
+Validation Ratcheting refers to the ability of the apiserver to accept updates
+to resources which fail validation, if the failing part of the resource was
+unchanged by the update operation.
+
+This feature allows authors of CRDs to confidently add new validations to the
+OpenAPIV3 schema under certain conditions. Users can update to the new schema
+safely without bumping the version of the object or breaking workflows.
+
+While most validations placed in the OpenAPIV3 schema of a CRD are support
+ratcheting, there are a few exceptions. The following OpenAPIV3 schema
+validations are not supported by ratcheting under the current implementation
+and if violated will continue to throw an error as normally:
+
+- Quantors
+ - `allOf`
+ - `oneOf`
+ - `anyOf`
+ - `not`
+ - any validations in a descendent of one of these fields
+- `x-kubernetes-validations`
+ CRD Validation Rules are currently ignored by ratcheting. This may be subject
+ to change.
+- `x-kubernetes-list-type`
+ Errors arising from changing the list type of a subschema will not be
+ ratcheted. For example adding `set` onto a list with duplicates will always
+ result in an error.
+- x-kubernetes-map-keys
+ Errors arising from changing the map keys of a list schema will not be
+ ratcheted.
+- `required`
+ Required fields may not be safely added
+- `properties`
+ Properties may not be safely removed, but changes to validations in their
+ schemas and subschemas may be ratcheted
+- `additionalProperties`
+ To remove a previously specified `additionalProperties` validation will not be
+ ratcheted.
+
## Validation rules
From f602facca3e28d2119866e82770f1dbec695e3f4 Mon Sep 17 00:00:00 2001
From: Wilson Wu
Date: Mon, 7 Aug 2023 18:58:34 +0800
Subject: [PATCH 193/446] =?UTF-8?q?Sync=20Consider=20All=20Microservices?=
=?UTF-8?q?=20Vulnerable=20=20=E2=80=94=20And=20Monitor=20Their=20Behavior?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
.../index.md | 238 +++
.../security_behavior_figure_1.svg | 1627 +++++++++++++++++
.../security_behavior_figure_2.svg | 633 +++++++
3 files changed, 2498 insertions(+)
create mode 100644 content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/index.md
create mode 100644 content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_1.svg
create mode 100644 content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_2.svg
diff --git a/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/index.md b/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/index.md
new file mode 100644
index 0000000000..0e0951abcb
--- /dev/null
+++ b/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/index.md
@@ -0,0 +1,238 @@
+---
+layout: blog
+title: 考虑所有微服务的脆弱性并对其行为进行监控
+date: 2023-01-20
+slug: security-behavior-analysis
+---
+
+
+
+**作者**:David Hadas (IBM Research Labs)
+
+**译者**:Wilson Wu (DaoCloud)
+
+
+_本文对 DevOps 产生的错误安全意识做出提醒。开发和配置微服务时遵循安全最佳实践并不能让微服务不易被攻击。
+本文说明,即使所有已部署的微服务都容易被攻击,但仍然可以采取很多措施来确保微服务不被利用。
+本文解释了如何从安全角度对客户端和服务的行为进行分析,此处称为 **“安全行为分析”** ,
+可以对已部署的易被攻击的微服务进行保护。本文会引用 [Guard](http://knative.dev/security-guard),
+一个开源项目,对假定易被攻击的 Kubernetes 微服务的安全行为提供监测与控制。_
+
+
+随着网络攻击的复杂性不断加剧,部署云服务的组织持续追加网络安全投资,旨在提供安全且不易被攻击的服务。
+然而,网络安全投资的逐年增长并没有造成网络安全事件的同步减少。相反,网络安全事件的数量每年都在持续增长。
+显然,这些组织在这场斗争中注定会失败——无论付出多大努力来检测和消除已部署服务中的网络安全弱点,攻击者似乎总是占据上风。
+
+
+考虑到当前广泛传播的攻击工具、复杂的攻击者以及攻击者们不断增长的网络安全经济收益,
+在 2023 年,任何依赖于构建无漏洞、无弱点服务的网络安全战略显然都过于天真。看来唯一可行的策略是:
+
+
+➥ **承认你的服务容易被攻击!**
+
+
+换句话说,清醒地接受你永远无法创建完全无懈可击服务的事实。
+如果你的对手找到哪怕一个弱点作为切入点,你就输了!承认尽管你尽了最大努力,
+你的所有服务仍然容易被攻击,这是重要的第一步。接下来,本文将讨论你可以对此做些什么......
+
+
+## 如何保护微服务不被利用 {#how-to-protect-microservices-from-being-exploited}
+
+
+容易被攻击并不一定意味着你的服务将被利用。尽管你的服务在某些方面存在你不知道的漏洞,
+但攻击者仍然需要识别这些漏洞并利用它们。如果攻击者无法利用你服务的漏洞,你就赢了!
+换句话说,拥有无法利用的漏洞就意味着拥有无法坐实的风险。
+
+
+{{< figure src="security_behavior_figure_1.svg" alt="攻击者在服务中取得立足点的示意图" class="diagram-large" caption="图 1:攻击者在易被攻击的服务中取得立足点" >}}
+
+
+如上图所示,攻击者尚未在服务中取得立足点;也就是说,假设你的服务在第一天没有运行由攻击者控制的代码。
+在我们的示例中,该服务暴露给客户端的 API 中存在漏洞。为了获得初始立足点,
+攻击者使用恶意客户端尝试利用服务 API 的其中一个漏洞。恶意客户端发送一个操作触发服务的一些计划外行为。
+
+
+更具体地说,我们假设该服务容易受到 SQL 注入攻击。开发人员未能正确过滤用户输入,
+从而允许客户端发送会改变预期行为的值。在我们的示例中,如果客户端发送键为“username”且值为 **“tom or 1=1”** 的查询字符串,
+则客户端将收到所有用户的数据。要利用此漏洞需要客户端发送不规范的字符串作为值。
+请注意,良性用户不会发送带有空格或等号字符的字符串作为用户名,相反,他们通常会发送合法的用户名,
+例如可以定义为字符 a-z 的短序列。任何合法的用户名都不会触发服务计划外行为。
+
+
+在这个简单的示例中,人们已经可以识别检测和阻止开发人员故意(无意)留下的漏洞被尝试利用的很多机会,
+从而使该漏洞无法被利用。首先,恶意客户端的行为与良性客户端的行为不同,因为它发送不规范的请求。
+如果检测到并阻止这种行为变化,则该漏洞将永远不会到达服务。其次,响应于漏洞利用的服务行为不同于响应于常规请求的服务行为。
+此类行为可能包括对其他服务(例如数据存储)进行后续不规范调用、消耗不确定的时间来响应和/或以非正常的响应来回应恶意客户端
+(例如,在良性客户端定期发出请求的情况下,包含比正常发送更多的数据)。
+如果检测到服务行为变化,也将允许在利用尝试的不同阶段阻止利用。
+
+
+更一般而言:
+
+
+- 监控客户端的行为可以帮助检测和阻止针对服务 API 漏洞的利用。事实上,
+ 部署高效的客户端行为监控会使许多漏洞无法被利用,而剩余漏洞则很难实现。
+ 为了成功,攻击者需要创建一个无法从常规请求中检测到的利用方式。
+
+
+- 监视服务的行为可以帮助检测通过任何攻击媒介正在被利用的服务。
+ 由于攻击者需要确保服务行为无法从常规服务行为中被检测到,所以有效的服务行为监控限制了攻击者可能实现的目的。
+
+
+结合这两种方法可以为已部署的易被攻击的服务添加一个保护层,从而大大降低任何人成功利用任何已部署的易被攻击服务的可能性。
+接下来,让我们来确定需要使用安全行为监控的四个使用场景。
+
+
+## 使用场景 {#use-cases}
+
+
+从安全的角度来看,我们可以识别任何服务生命周期中的以下四个不同阶段。
+每个阶段都需要安全行为监控来应对不同的挑战:
+
+
+服务状态 | 使用场景 | 为了应对这个使用场景,你需要什么?
+------------- | ------------- | -----------------------------------------
+**正常的** | **无已知漏洞:** 服务所有者通常不知道服务镜像或配置中存在任何已知漏洞。然而,可以合理地假设该服务存在弱点。 | **针对任何未知漏洞、零日漏洞、服务本身漏洞提供通用保护** - 检测/阻止作为发送给客户端请求的可能被用作利用的部分不规则模式。
+**存在漏洞的** | **相关的 CVE 已被公开:** 服务所有者需要发布该服务的新的无漏洞修订版。研究表明,实际上,消除已知漏洞的过程可能需要数周才能完成(平均 2 个月)。 | **基于 CVE 分析添加保护** - 检测/阻止包含可用于利用已发现漏洞特定模式的请求。尽管该服务存在已知漏洞,但仍然继续提供服务。
+**可被利用的** | **可利用漏洞已被公开:** 服务所有者需要一种方法来过滤包含已知可利用漏洞的传入请求。 | **基于已知的可利用漏洞签名添加保护** - 检测/阻止携带识别可利用漏洞签名的传入客户端请求。尽管存在可利用漏洞,但仍继续提供服务。
+**已被不当使用的** | **攻击者不当使用服务背后的 Pod:** 攻击者可以遵循某种攻击模式,从而使他/她能够对 Pod 进行不当使用。服务所有者需要重新启动任何受损的 Pod,同时使用未受损的 Pod 继续提供服务。请注意,一旦 Pod 重新启动,攻击者需要重复进行攻击,然后才能再次对其进行不当使用。 | **识别并重新启动被不当使用的组件实例** - 在任何给定时间,某些后端的 Pod 可能会受到损害和不当使用,而其他后端 Pod 则按计划运行。检测/删除被不当使用的 Pod,同时允许其他 Pod 继续为客户端请求提供服务。
+
+
+而幸运的是,微服务架构非常适合接下来讨论的安全行为监控。
+
+
+## 微服务与单体的安全行为对比 {#microservices-vs-monoliths}
+
+
+Kubernetes 通常提供用于支持微服务架构设计的工作负载。在设计上,微服务旨在遵循“做一件事并将其做好”的 UNIX 哲学。
+每个微服务都有一个有边界的上下文和一个清晰的接口。换句话说,你可以期望微服务客户端发送相对规范的请求,
+并且微服务呈现相对规范的行为作为对这些请求的响应。因此,微服务架构是安全行为监控的绝佳候选者。
+
+
+{{< figure src="security_behavior_figure_2.svg" alt="该图显示了为什么微服务非常适合安全行为监控" class="diagram-large" caption="图 2:微服务非常适合安全行为监控" >}}
+
+
+上图阐明了将单体服务划分为一组微服务是如何提高我们执行安全行为监测和控制的能力。
+在单体服务方法中,不同的客户端请求交织在一起,导致识别不规则客户端行为的能力下降。
+在没有先验知识的情况下,观察者将发现很难区分交织在一起的客户端请求的类型及其相关特征。
+此外,内部客户端请求不会暴露给观察者。最后,单体服务的聚合行为是其组件的许多不同内部行为的复合体,因此很难识别不规范的服务行为。
+
+
+在微服务环境中,每个微服务在设计上都期望提供定义更明确的服务,并服务于定义更明确的请求类型。
+这使得观察者更容易识别不规范的客户端行为和不规范的服务行为。此外,微服务设计公开了内部请求和内部服务,
+从而提供更多安全行为数据来识别观察者的违规行为。总的来说,这使得微服务设计模式更适合安全行为监控。
+
+
+## Kubernetes 上的安全行为监控 {#security-behavior-monitoring-on-kubernetes}
+
+
+寻求添加安全行为的 Kubernetes 部署可以使用在 CNCF Knative 项目下开发的 [Guard](http://knative.dev/security-guard)。
+Guard 集成到在 Kubernetes 之上运行的完整 Knative 自动化套件中。或者,
+**你可以将 Guard 作为独立工具部署**,以保护 Kubernetes 上任何基于 HTTP 的工作负载。
+
+
+查看:
+
+
+- Github 上的 [Guard](https://github.com/knative-sandbox/security-guard),用于将 Guard 用作独立工具。
+- Knative 自动化套件 - 在博客文章 [Opinionated Kubernetes](https://davidhadas.wordpress.com/2022/08/29/knative-an-opinionated-kubernetes) 中了解 Knative,
+ 其中描述了 Knative 如何简化和统一 Web 服务在 Kubernetes 上的部署方式。
+- 你可以在 [SIG Security](https://kubernetes.slack.com/archives/C019LFTGNQ3)
+ 或 Knative 社区 [Security](https://knative.slack.com/archives/CBYV1E0TG) Slack 频道上联系 Guard 维护人员。
+ Knative 社区频道将很快转移到 [CNCF Slack](https://communityinviter.com/apps/cloud-native/cncf),其名称为`#knative-security`。
+
+
+本文的目标是邀请 Kubernetes 社区采取行动,并引入安全行为监测和控制,
+以帮助保护基于 Kubernetes 的部署。希望社区后续能够:
+
+
+1. 分析不同 Kubernetes 使用场景带来的网络挑战
+1. 为用户添加适当的安全文档,介绍如何引入安全行为监控。
+1. 考虑如何与帮助用户监测和控制其易被攻击服务的工具进行集成。
+
+
+## 欢迎参与 {#getting-involved}
+
+
+欢迎你参与到对 Kubernetes 的开发安全行为监控的工作中;以代码或文档的形式分享反馈或做出贡献;并以任何形式完成或提议相关改进。
diff --git a/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_1.svg b/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_1.svg
new file mode 100644
index 0000000000..36905d5a8d
--- /dev/null
+++ b/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_1.svg
@@ -0,0 +1,1627 @@
+
+
+
+
diff --git a/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_2.svg b/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_2.svg
new file mode 100644
index 0000000000..2079b94129
--- /dev/null
+++ b/content/zh-cn/blog/_posts/2023-01-20-Security-Bahavior-Analysis/security_behavior_figure_2.svg
@@ -0,0 +1,633 @@
+
+
+
+
From 98b52d510b800f82bd2da18e27708a087ac400af Mon Sep 17 00:00:00 2001
From: Tim Bannister
Date: Tue, 8 Aug 2023 09:02:44 +0200
Subject: [PATCH 194/446] dra: cleanup of Kubernetes 1.28 update
This is a follow-up to https://github.com/kubernetes/website/pull/41856 with
the suggested enhancements.
---
.../scheduling-eviction/dynamic-resource-allocation.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 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 e4bc0eac98..f34f7a2c5a 100644
--- a/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
+++ b/content/en/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md
@@ -170,7 +170,7 @@ running Pods. For more information on the gRPC endpoints, see the
## Pre-scheduled Pods
-When creating a Pod with `nodeName` already set, the scheduler gets bypassed.
+When you - or another API client - create a Pod with `spec.nodeName` already set, the scheduler gets bypassed.
If some ResourceClaim needed by that Pod does not exist yet, is not allocated
or not reserved for the Pod, then the kubelet will fail to run the Pod and
re-check periodically because those requirements might still get fulfilled
@@ -182,11 +182,11 @@ was not enabled in the scheduler at the time when the Pod got scheduled
detects this and tries to make the Pod runnable by triggering allocation and/or
reserving the required ResourceClaims.
-However, it is better to avoid this because a Pod which is assigned to a node
+However, it is better to avoid this because a Pod that is assigned to a node
blocks normal resources (RAM, CPU) that then cannot be used for other Pods
while the Pod is stuck. To make a Pod run on a specific node while still going
through the normal scheduling flow, create the Pod with a node selector that
-matches exactly the desired node:
+exactly matches the desired node:
```yaml
apiVersion: v1
@@ -199,6 +199,9 @@ spec:
...
```
+You may also be able to mutate the incoming Pod, at admission time, to unset
+the `.spec.nodeName` field and to use a node selector instead.
+
## Enabling dynamic resource allocation
Dynamic resource allocation is an *alpha feature* and only enabled when the
From 498e518cc992be348f06382a6ac85315300531f9 Mon Sep 17 00:00:00 2001
From: Joshua Su
Date: Tue, 8 Aug 2023 19:59:58 +0800
Subject: [PATCH 195/446] Fix a small error of example config
Signed-off-by: Joshua Su
---
content/en/docs/reference/config-api/kubeadm-config.v1beta3.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 5504f6070e..2e7fd8319d 100644
--- a/content/en/docs/reference/config-api/kubeadm-config.v1beta3.md
+++ b/content/en/docs/reference/config-api/kubeadm-config.v1beta3.md
@@ -218,7 +218,7 @@ configuration types to be used during a kubeadm init run.
pathType:Filescheduler:extraArgs:
-address:"10.100.0.1"
+bind-address:"10.100.0.1"extraVolumes:- name:"some-volume"hostPath:"/etc/some-path"
From 96a8055b0502cd3bf20a454c364a6630c246b08d Mon Sep 17 00:00:00 2001
From: Joshua Su
Date: Tue, 8 Aug 2023 22:34:11 +0800
Subject: [PATCH 196/446] [zh-cn]sync commit
#498e518cc992be348f06382a6ac85315300531f9
Signed-off-by: Joshua Su
---
.../zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md b/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md
index ae8529e563..a2b0896d1c 100644
--- a/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md
+++ b/content/zh-cn/docs/reference/config-api/kubeadm-config.v1beta3.md
@@ -377,7 +377,7 @@ https://pkg.go.dev/k8s.io/kubelet/config/v1beta1#KubeletConfiguration。
pathType:Filescheduler:extraArgs:
-address:"10.100.0.1"
+bind-address:"10.100.0.1"extraVolumes:- name:"some-volume"hostPath:"/etc/some-path"
From 4dfef3e53f2d78a1be598a052d2c625e99fe4590 Mon Sep 17 00:00:00 2001
From: Jiahui Feng
Date: Tue, 8 Aug 2023 07:52:16 -0700
Subject: [PATCH 197/446] Document ValidatingAdmissionPolicy variable
composition and namespaceObject (#42220)
* variable composition.
* mention namespaceObject.
* Apply suggestions from code review
Co-authored-by: Tim Bannister
* separate commands from output.
* YAML comment.
* Update content/en/docs/reference/access-authn-authz/validating-admission-policy.md
Co-authored-by: Tim Bannister
* no shell prompt.
* Update content/en/docs/reference/access-authn-authz/validating-admission-policy.md
Co-authored-by: Joe Betz
* Update content/en/docs/reference/access-authn-authz/validating-admission-policy.md
Co-authored-by: Joe Betz
---------
Co-authored-by: Tim Bannister
Co-authored-by: Joe Betz
---
.../validating-admission-policy.md | 42 ++++++++++++++++++-
...-matches-namespace-environment.policy.yaml | 28 +++++++++++++
2 files changed, 68 insertions(+), 2 deletions(-)
create mode 100644 content/en/examples/access/image-matches-namespace-environment.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 a9c802b605..8b743e8e9f 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
@@ -334,6 +334,8 @@ 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.
+- `namespaceObject` - The namespace, as a Kubernetes resource, that the incoming object belongs to.
+ The value is null if the incoming object is cluster-scoped.
- `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
@@ -465,8 +467,8 @@ event and all other values will be ignored.
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.
+a message expression has access to `object`, `oldObject`, `request`, `params`, and `namespaceObject`.
+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:
@@ -578,3 +580,39 @@ Type Checking has the following limitation:
- 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.
+
+### Variable composition
+
+If an expression grows too complicated, or part of the expression is reusable and computationally expensive to evaluate,
+you can extract some part of the expressions into variables. A variable is a named expression that can be referred later
+in `variables` in other expressions.
+
+```yaml
+spec:
+ variables:
+ - name: foo
+ expression: "'foo' in object.spec.metadata.labels ? object.spec.metadata.labels['foo'] : 'default'"
+ validations:
+ - expression: variables.foo == 'bar'
+```
+
+A variable is lazily evaluated when it is first referred. Any error that occurs during the evaluation will be
+reported during the evaluation of the referring expression. Both the result and potential error are memorized and
+count only once towards the runtime cost.
+
+The order of variables are important because a variable can refer to other variables that are defined before it.
+This ordering prevents circular references.
+
+The following is a more complex example of enforcing that image repo names match the environment defined in its namespace.
+
+{{< codenew file="access/image-matches-namespace-environment.policy.yaml" >}}
+
+With the policy bound to the namespace `default`, which is labeled `environment: prod`,
+the following attempt to create a deployment would be rejected.
+```shell
+kubectl create deploy --image=dev.example.com/nginx invalid
+```
+The error message is similar to this.
+```console
+error: failed to create deployment: deployments.apps "invalid" is forbidden: ValidatingAdmissionPolicy 'image-matches-namespace-environment.policy.example.com' with binding 'demo-binding-test.example.com' denied request: only prod images are allowed in namespace default
+```
\ No newline at end of file
diff --git a/content/en/examples/access/image-matches-namespace-environment.policy.yaml b/content/en/examples/access/image-matches-namespace-environment.policy.yaml
new file mode 100644
index 0000000000..1a3da26898
--- /dev/null
+++ b/content/en/examples/access/image-matches-namespace-environment.policy.yaml
@@ -0,0 +1,28 @@
+# This policy enforces that all containers of a deployment has the image repo match the environment label of its namespace.
+# Except for "exempt" deployments, or any containers that do not belong to the "example.com" organization (e.g. common sidecars).
+# For example, if the namespace has a label of {"environment": "staging"}, all container images must be either staging.example.com/*
+# or do not contain "example.com" at all, unless the deployment has {"exempt": "true"} label.
+apiVersion: admissionregistration.k8s.io/v1beta1
+kind: ValidatingAdmissionPolicy
+metadata:
+ name: "image-matches-namespace-environment.policy.example.com"
+spec:
+ failurePolicy: Fail
+ matchConstraints:
+ resourceRules:
+ - apiGroups: ["apps"]
+ apiVersions: ["v1"]
+ operations: ["CREATE", "UPDATE"]
+ resources: ["deployments"]
+ variables:
+ - name: environment
+ expression: "'environment' in namespaceObject.metadata.labels ? namespaceObject.metadata.labels['environment'] : 'prod'"
+ - name: exempt
+ expression: "'exempt' in object.metadata.labels && object.metadata.labels['exempt'] == 'true'"
+ - name: containers
+ expression: "object.spec.template.spec.containers"
+ - name: containersToCheck
+ expression: "variables.containers.filter(c, c.image.contains('example.com/'))"
+ validations:
+ - expression: "variables.exempt || variables.containersToCheck.all(c, c.image.startsWith(variables.environment + '.'))"
+ messageExpression: "'only ' + variables.environment + ' images are allowed in namespace ' + namespaceObject.metadata.name"
\ No newline at end of file
From 75ec81802226dc4a8300146f22f11e6e0230b933 Mon Sep 17 00:00:00 2001
From: Alexander Zielenski <351783+alexzielenski@users.noreply.github.com>
Date: Tue, 8 Aug 2023 08:53:42 -0700
Subject: [PATCH 198/446] feedback
---
.../custom-resource-definitions.md | 35 +++++++++++--------
1 file changed, 21 insertions(+), 14 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 b3278af65c..9ca480618b 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
@@ -717,15 +717,21 @@ And create it:
kubectl apply -f my-crontab.yaml
crontab "my-new-cron-object" created
```
-### Validation Ratcheting
+### Validation ratcheting
-Validation Ratcheting is alpha since 1.28. Enable the `CRDValidationRatcheting`
+{{< feature-state state="alpha" for_k8s_version="v1.28" >}}
+
+You need to enable the `CRDValidationRatcheting`
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to
-use the feature.
+use this behavior, which then applies to all CustomResourceDefinitions in your
+cluster.
-Validation Ratcheting refers to the ability of the apiserver to accept updates
-to resources which fail validation, if the failing part of the resource was
-unchanged by the update operation.
+Provided you enabled the feature gate, Kubernetes implements _validation racheting_
+for CustomResourceDefinitions. The API server is willing accept updates to resources that
+are not valid after the update, provided that each part of the resource that failed to validate
+was not changed by the update operation. In other words, any invalid part of the resource
+that remains invalid must have already been wrong.
+You cannot use this mechanism to update a valid resource so that it becomes invalid.
This feature allows authors of CRDs to confidently add new validations to the
OpenAPIV3 schema under certain conditions. Users can update to the new schema
@@ -733,8 +739,8 @@ safely without bumping the version of the object or breaking workflows.
While most validations placed in the OpenAPIV3 schema of a CRD are support
ratcheting, there are a few exceptions. The following OpenAPIV3 schema
-validations are not supported by ratcheting under the current implementation
-and if violated will continue to throw an error as normally:
+validations are not supported by ratcheting under the implementation in Kubernetes
+{{< skew currentVersion >}} and if violated will continue to throw an error as normally:
- Quantors
- `allOf`
@@ -743,20 +749,21 @@ and if violated will continue to throw an error as normally:
- `not`
- any validations in a descendent of one of these fields
- `x-kubernetes-validations`
- CRD Validation Rules are currently ignored by ratcheting. This may be subject
- to change.
+ For Kubernetes {{< skew currentVersion >}}, CRD validation rules](#validation-rules) are ignored by
+ ratcheting. This may change in later Kubernetes releases.
- `x-kubernetes-list-type`
Errors arising from changing the list type of a subschema will not be
ratcheted. For example adding `set` onto a list with duplicates will always
result in an error.
-- x-kubernetes-map-keys
+- `x-kubernetes-map-keys`
Errors arising from changing the map keys of a list schema will not be
ratcheted.
- `required`
- Required fields may not be safely added
+ Errors arising from changing the list of required fields will not be ratcheted.
- `properties`
- Properties may not be safely removed, but changes to validations in their
- schemas and subschemas may be ratcheted
+ Adding/removing/modifying the names of properties is not ratcheted, but
+ changes to validations in each properties' schemas and subschemas may be ratcheted
+ if the name of the property stays the same.
- `additionalProperties`
To remove a previously specified `additionalProperties` validation will not be
ratcheted.
From 2218f3d573f33066d4ed943e0bccecb82049ec6b Mon Sep 17 00:00:00 2001
From: Amine
Date: Tue, 8 Aug 2023 20:02:35 +0200
Subject: [PATCH 199/446] Remove note stating that we need
AdmissionWebhookMatchConditions to be enabled explicitely
---
.../access-authn-authz/extensible-admission-controllers.md | 5 -----
1 file changed, 5 deletions(-)
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 73b29690f4..7f6cdc04df 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
@@ -723,11 +723,6 @@ The `matchPolicy` for an admission webhooks defaults to `Equivalent`.
{{< feature-state state="beta" for_k8s_version="v1.28" >}}
-{{< 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
From a92606ec8c94842f3b47e60eb48a02985708aae8 Mon Sep 17 00:00:00 2001
From: Tim Bannister
Date: Tue, 8 Aug 2023 19:12:34 +0100
Subject: [PATCH 200/446] Fix punctuation
---
.../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 734d8ea0b7..59429ef216 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
@@ -453,7 +453,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
allowing you to scrape health check metrics.
- `ConsistentHTTPGetHandlers`: Normalize HTTP get URL and Header passing for lifecycle
handlers with probers.
-- `ConsistentListFromCache`: Allow the API server to serve consistent lists from cache
+- `ConsistentListFromCache`: Allow the API server to serve consistent lists from cache.
- `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
From ed64c34779797ae7269252a2e18cabb23810e952 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Fri, 7 Jul 2023 07:55:29 -0400
Subject: [PATCH 201/446] placeholder for blog
---
content/en/blog/_posts/2023-job-update-post.md | 6 ++++++
1 file changed, 6 insertions(+)
create mode 100644 content/en/blog/_posts/2023-job-update-post.md
diff --git a/content/en/blog/_posts/2023-job-update-post.md b/content/en/blog/_posts/2023-job-update-post.md
new file mode 100644
index 0000000000..7cde385bce
--- /dev/null
+++ b/content/en/blog/_posts/2023-job-update-post.md
@@ -0,0 +1,6 @@
+---
+layout: blog
+title: "Kubernetes 1.28: Updates to the Job API"
+date: 2023-08-20T10:00:00-08:00
+slug: kubernetes-1-28-podreplacementpolicy-backoffconfigs
+---
From 4dc0ff70d4ad50576aed5a4b908cd6a295f95c0d Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Thu, 27 Jul 2023 17:20:45 -0400
Subject: [PATCH 202/446] add pod recreation policy to the blog post
---
.../en/blog/_posts/2023-job-update-post.md | 63 ++++++++++++++++++-
1 file changed, 61 insertions(+), 2 deletions(-)
diff --git a/content/en/blog/_posts/2023-job-update-post.md b/content/en/blog/_posts/2023-job-update-post.md
index 7cde385bce..a006ca2f76 100644
--- a/content/en/blog/_posts/2023-job-update-post.md
+++ b/content/en/blog/_posts/2023-job-update-post.md
@@ -1,6 +1,65 @@
---
layout: blog
title: "Kubernetes 1.28: Updates to the Job API"
-date: 2023-08-20T10:00:00-08:00
-slug: kubernetes-1-28-podreplacementpolicy-backoffconfigs
+date: 2023-07-27
+slug: kubernetes-1-28-jobapi-update
---
+
+**Authors:** Kevin Hannon (G-Research), Michał Woźniak (Google)
+
+This blog discusses two features to improve Jobs for batch users: PodRecreationPolicy and JobBackoffLimitPerIndex.
+
+These are two features requested from users of the Job API to enhance a user's experience.
+
+## Pod Recreation Policy
+
+### What problem does this solve?
+
+Many common machine learning frameworks, such as Tensorflow and JAX, require unique pods per Index. Currently, if a pod enters a terminating state (due to preemption, eviction or other external factors), a replacement pod is created and immediately fail to start.
+
+Having a replacement Pod before the previous one fully terminates can also cause problems in clusters with scarce resources or with tight budgets. These resources can be difficult to obtain so pods can take a long time to find resources and they may only be able to find nodes once the existing pods have been terminated. If cluster autoscaler is enabled, the replacement Pods might produce undesired scale ups.
+
+On the other hand, if a replacement Pod is not immediately created, the Job status would show that the number of active pods doesn't match the desired parallelism. To provide better visibility, the job status can have a new field to track the number of Pods currently terminating.
+
+This new field can also be used by queueing controllers, such as Kueue, to track the number of terminating pods to calculate quotas.
+
+### How can I use it
+
+This is an alpha feature, which means you have to enable the `JobPodReplacementPolicy`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
+with the command line argument `--feature-gates=JobPodReplacementPolicy=true`
+to the kube-apiserver.
+
+```yaml
+kind: Job
+metadata:
+ name: new
+ ...
+spec:
+ podReplacementPolicy: Failed
+ ...
+```
+
+`podReplacementPolicy` can take either `Failed` or `TerminatingOrFailed`. In cases where `PodFailurePolicy` is set, you can only use `Failed`.
+
+This feature enables two components in the Job controller: Adds a `terminating` field to the status and adds a new API field called `podReplacementPolicy`.
+
+The Job controller uses `parallelism` field in the Job API to determine the number of pods that it is expects to be active (not finished). If there is a mismatch of active pods and the pod has not finished, we would normally assume that the pod has failed and the Job controller would recreate the pod. In cases where `Failed` is specified, the Job controller will wait for the pod to be fully terminated (`DeletionTimeStamp != nil`).
+
+### How can I learn more?
+
+- Read the KEP: [PodReplacementPolicy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3939-allow-replacement-when-fully-terminated)
+
+## JobBackoffLimitPerIndex
+
+### Getting Involved
+
+These features were sponsored under the domain of SIG Apps. Batch is actively being improved for Kubernetes users in the batch working group.
+Working groups are relatively short-lived initatives focused on specific goals. In the case of Batch, the goal is to improve/support batch users and enhance the Job API for common use cases. If that interests you, please join the working group either by subscriping to our [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-batch) or on [Slack](https://kubernetes.slack.com/messages/wg-batch).
+
+### Acknowledgments
+
+As with any Kubernetes feature, multiple people contributed to getting this
+done, from testing and filing bugs to reviewing code.
+
+We would not have been able to achieve either of these features without Aldo Culquicondor (Google) providing excellent domain knowledge and expertise throughout the Kubernetes ecosystem.
From 8aaded80c9be267de5b2f25910542a588a2a577d Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Thu, 27 Jul 2023 17:46:19 -0400
Subject: [PATCH 203/446] update blog post with name with date
---
.../{2023-job-update-post.md => 2023-07-27-job-update-post.md} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename content/en/blog/_posts/{2023-job-update-post.md => 2023-07-27-job-update-post.md} (100%)
diff --git a/content/en/blog/_posts/2023-job-update-post.md b/content/en/blog/_posts/2023-07-27-job-update-post.md
similarity index 100%
rename from content/en/blog/_posts/2023-job-update-post.md
rename to content/en/blog/_posts/2023-07-27-job-update-post.md
From 35565dfe33fe49aa9aa22cb7d8e46d275b76134b Mon Sep 17 00:00:00 2001
From: Michal Wozniak
Date: Fri, 4 Aug 2023 17:23:32 +0200
Subject: [PATCH 204/446] backoff limit per index
Co-authored-by: Kevin Hannon
---
.../blog/_posts/2023-07-27-job-update-post.md | 186 +++++++++++++++---
1 file changed, 164 insertions(+), 22 deletions(-)
diff --git a/content/en/blog/_posts/2023-07-27-job-update-post.md b/content/en/blog/_posts/2023-07-27-job-update-post.md
index a006ca2f76..29820b5d39 100644
--- a/content/en/blog/_posts/2023-07-27-job-update-post.md
+++ b/content/en/blog/_posts/2023-07-27-job-update-post.md
@@ -1,34 +1,43 @@
---
layout: blog
-title: "Kubernetes 1.28: Updates to the Job API"
-date: 2023-07-27
+title: "Kubernetes 1.28: New Job features"
+date: 2023-08-15
slug: kubernetes-1-28-jobapi-update
---
**Authors:** Kevin Hannon (G-Research), Michał Woźniak (Google)
-This blog discusses two features to improve Jobs for batch users: PodRecreationPolicy and JobBackoffLimitPerIndex.
+This blog discusses two new features in Kubernetes 1.28 to improve Jobs for batch
+users: [PodReplacementPolicy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3939-allow-replacement-when-fully-terminated)
+and [BackoffLimitPerIndex](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3850-backoff-limits-per-index-for-indexed-jobs).
-These are two features requested from users of the Job API to enhance a user's experience.
-
-## Pod Recreation Policy
+## Pod Replacement Policy
### What problem does this solve?
-Many common machine learning frameworks, such as Tensorflow and JAX, require unique pods per Index. Currently, if a pod enters a terminating state (due to preemption, eviction or other external factors), a replacement pod is created and immediately fail to start.
+By default, when a pod enters a terminating state (e.g. due to preemption or
+eviction), a replacement pod is created immediately, and both pods are running
+at the same time.
-Having a replacement Pod before the previous one fully terminates can also cause problems in clusters with scarce resources or with tight budgets. These resources can be difficult to obtain so pods can take a long time to find resources and they may only be able to find nodes once the existing pods have been terminated. If cluster autoscaler is enabled, the replacement Pods might produce undesired scale ups.
+This is problematic for some popular machine learning frameworks, such as
+TensorFlow and [JAX](https://jax.readthedocs.io/en/latest/), which require at most one pod running at the same time,
+for a given index (see more details in the [issue](https://github.com/kubernetes/kubernetes/issues/115844)).
-On the other hand, if a replacement Pod is not immediately created, the Job status would show that the number of active pods doesn't match the desired parallelism. To provide better visibility, the job status can have a new field to track the number of Pods currently terminating.
-
-This new field can also be used by queueing controllers, such as Kueue, to track the number of terminating pods to calculate quotas.
+Creating the replacement Pod before the previous one fully terminates can also
+cause problems in clusters with scarce resources or with tight budgets. These
+resources can be difficult to obtain so pods can take a long time to find
+resources and they may only be able to find nodes until the existing pods are
+fully terminated. Further, if cluster autoscaler is enabled, the replacement
+Pods might produce undesired scale ups.
### How can I use it
-This is an alpha feature, which means you have to enable the `JobPodReplacementPolicy`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
-with the command line argument `--feature-gates=JobPodReplacementPolicy=true`
-to the kube-apiserver.
+This is an alpha feature, which you can enable by enabling the `JobPodReplacementPolicy`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in
+your cluster.
+
+Once the feature is enabled you can use it by creating a new Job, which specifies
+`podReplacementPolicy` field as shown here:
```yaml
kind: Job
@@ -40,26 +49,159 @@ spec:
...
```
-`podReplacementPolicy` can take either `Failed` or `TerminatingOrFailed`. In cases where `PodFailurePolicy` is set, you can only use `Failed`.
+Additionally, you can inspect the `.status.terminating` field of a Job. The value
+of the field is the number of Pods owned by the Job that are currently terminating.
-This feature enables two components in the Job controller: Adds a `terminating` field to the status and adds a new API field called `podReplacementPolicy`.
+```shell
+kubectl get jobs/myjob -o yaml
+```
-The Job controller uses `parallelism` field in the Job API to determine the number of pods that it is expects to be active (not finished). If there is a mismatch of active pods and the pod has not finished, we would normally assume that the pod has failed and the Job controller would recreate the pod. In cases where `Failed` is specified, the Job controller will wait for the pod to be fully terminated (`DeletionTimeStamp != nil`).
+```yaml
+apiVersion: batch/v1
+kind: Job
+status:
+ terminating: 3 # three Pods are terminating and have not yet reached the Failed phase
+```
+
+This can be particularly useful for external queueing controllers, such as
+[Kueue](https://github.com/kubernetes-sigs/kueue), that would calculate the
+quota and suspend the start of a new Job until the resources are reclaimed from
+the currently terminating Job.
### How can I learn more?
- Read the KEP: [PodReplacementPolicy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3939-allow-replacement-when-fully-terminated)
-## JobBackoffLimitPerIndex
+## Job Backoff Limit per Index
+
+### What problem does this solve?
+
+By default, pod failures for [Indexed Jobs](/docs/concepts/workloads/controllers/job/#completion-mode)
+are counted towards the global limit of retries, represented by `.spec.backoffLimit`.
+This means, that if there is a consistently failing index, it is restarted
+repeatedly until it exhausts the limit. Once the limit is exceeded the entire
+Job is marked failed and some indexes may never be even started.
+
+This is problematic for use cases where you want to handle pod failures for
+every index independently. For example, if you use Indexed Jobs for running
+integration tests where each index corresponds to a testing suite. In that case,
+you may want to account for possible flake tests allowing for 1 or 2 retries per
+suite. Additionally, there might be some buggy suites, making the corresponding
+indexes fail consistently. In that case you may prefer to terminate retries for
+that indexes, yet allowing other suites to complete.
+
+The feature allows you to:
+* complete execution of all indexes, despite some indexes failing,
+* better utilize the computational resources by avoiding unnecessary retries of consistently failing indexes.
+
+### How to use it?
+
+This is an alpha feature, which you can enable by enabling the
+`JobBackoffLimitPerIndex`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+in your cluster.
+
+Once the feature is enabled, you can create an Indexed Job with the
+`.spec.backoffLimitPerIndex` field specified.
+
+#### Example
+
+The following example demonstrates how to use this feature to make sure the
+Job executes all indexes, and the number of failures is controller per index.
+
+```yaml
+apiVersion: batch/v1
+kind: Job
+metadata:
+ name: job-backoff-limit-per-index-execute-all
+spec:
+ completions: 8
+ parallelism: 2
+ completionMode: Indexed
+ backoffLimitPerIndex: 1
+ template:
+ spec:
+ restartPolicy: Never
+ containers:
+ - name: example
+ image: python
+ command:
+ - python3
+ - -c
+ - |
+ import os, sys, time
+ id = int(os.environ.get("JOB_COMPLETION_INDEX"))
+ if id == 1 or id == 2:
+ sys.exit(1)
+ time.sleep(1)
+```
+
+Now, inspect the pods after the job is finished:
+
+```sh
+kubectl get pods -l job-name=job-backoff-limit-per-index-execute-all
+```
+
+Returns output similar to this:
+```
+NAME READY STATUS RESTARTS AGE
+job-backoff-limit-per-index-execute-all-0-b26vc 0/1 Completed 0 49s
+job-backoff-limit-per-index-execute-all-1-6j5gd 0/1 Error 0 49s
+job-backoff-limit-per-index-execute-all-1-6wd82 0/1 Error 0 37s
+job-backoff-limit-per-index-execute-all-2-c66hg 0/1 Error 0 32s
+job-backoff-limit-per-index-execute-all-2-nf982 0/1 Error 0 43s
+job-backoff-limit-per-index-execute-all-3-cxmhf 0/1 Completed 0 33s
+job-backoff-limit-per-index-execute-all-4-9q6kq 0/1 Completed 0 28s
+job-backoff-limit-per-index-execute-all-5-z9hqf 0/1 Completed 0 28s
+job-backoff-limit-per-index-execute-all-6-tbkr8 0/1 Completed 0 23s
+job-backoff-limit-per-index-execute-all-7-hxjsq 0/1 Completed 0 22s
+```
+
+Additionally, let's take a look at the job status:
+
+```sh
+kubectl get jobs job-backoff-limit-per-index-fail-index -o yaml
+```
+
+Returns output similar to this:
+
+```yaml
+ status:
+ completedIndexes: 0,3-7
+ failedIndexes: 1,2
+ succeeded: 6
+ failed: 4
+ conditions:
+ - message: Job has failed indexes
+ reason: FailedIndexes
+ status: "True"
+ type: Failed
+```
+
+Here, indexes `1` and `2` were both retried once. After the second failure,
+in each of them, the specified `.spec.backoffLimitPerIndex` was exceeded, so
+the retries were stopped. For comparison, if the per-index backoff was disabled,
+then the buggy indexes would retry until the global `backoffLimit` was exceeded,
+and then the entire Job would be marked failed, before some of the higher
+indexes are started.
### Getting Involved
-These features were sponsored under the domain of SIG Apps. Batch is actively being improved for Kubernetes users in the batch working group.
-Working groups are relatively short-lived initatives focused on specific goals. In the case of Batch, the goal is to improve/support batch users and enhance the Job API for common use cases. If that interests you, please join the working group either by subscriping to our [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-batch) or on [Slack](https://kubernetes.slack.com/messages/wg-batch).
+These features were sponsored under the domain of SIG Apps. Batch is actively
+being improved for Kubernetes users in the
+[batch working group](https://github.com/kubernetes/community/tree/master/wg-batch).
+Working groups are relatively short-lived initiatives focused on specific goals.
+In the case of Batch, the goal is to improve/support batch users and enhance the
+Job API for common use cases. If that interests you, please join the working
+group either by subscriping to our
+[mailing list](https://groups.google.com/a/kubernetes.io/g/wg-batch) or on
+[Slack](https://kubernetes.slack.com/messages/wg-batch).
### Acknowledgments
As with any Kubernetes feature, multiple people contributed to getting this
done, from testing and filing bugs to reviewing code.
-We would not have been able to achieve either of these features without Aldo Culquicondor (Google) providing excellent domain knowledge and expertise throughout the Kubernetes ecosystem.
+We would not have been able to achieve either of these features without Aldo
+Culquicondor (Google) providing excellent domain knowledge and expertise
+throughout the Kubernetes ecosystem.
From 10026321ee8418804bf9c13b87ddd4785d9e6a16 Mon Sep 17 00:00:00 2001
From: Heba Elayoty
Date: Tue, 8 Aug 2023 12:02:19 -0700
Subject: [PATCH 205/446] move the missing lines
Signed-off-by: Heba Elayoty
---
.../en/docs/reference/labels-annotations-taints/_index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index cd38f57f02..df8d16f65a 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -1057,6 +1057,9 @@ Used on: Pod
The Job controller in the kube-controller-manager sets this as a label and annotation for Pods
created with Indexed [completion mode](/docs/concepts/workloads/controllers/job/#completion-mode).
+Note the [PodIndexLabel](content/en/docs/reference/command-line-tools-reference/feature-gates.md) feature gate must be enabled
+for this to be added as a pod **label**, otherwise it will just be an annotation.
+
### batch.kubernetes.io/cronjob-scheduled-timestamp
Type: Annotation
@@ -1070,9 +1073,6 @@ when that Job is part of a CronJob.
The control plane sets the value to that timestamp in RFC3339 format. If the Job belongs to a CronJob
with a timezone specified, then the timestamp is in that timezone. Otherwise, the timestamp is in controller-manager's local time.
-Note the [PodIndexLabel](content/en/docs/reference/command-line-tools-reference/feature-gates.md) feature gate must be enabled
-for this to be added as a pod **label**, otherwise it will just be an annotation.
-
### kubectl.kubernetes.io/default-container
Type: Annotation
From b2f2031229dd93bedf695ae63476fe8e388e6f40 Mon Sep 17 00:00:00 2001
From: Rey Lejano
Date: Tue, 8 Aug 2023 12:52:05 -0700
Subject: [PATCH 206/446] update blog publish date for 1.28 feature blog for
non graceful node shutdown blog
---
...-to-ga.md => 2023-08-16-non-graceful-node-shutdown-to-ga.md} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename content/en/blog/_posts/{2023-08-15-non-graceful-node-shutdown-to-ga.md => 2023-08-16-non-graceful-node-shutdown-to-ga.md} (99%)
diff --git a/content/en/blog/_posts/2023-08-15-non-graceful-node-shutdown-to-ga.md b/content/en/blog/_posts/2023-08-16-non-graceful-node-shutdown-to-ga.md
similarity index 99%
rename from content/en/blog/_posts/2023-08-15-non-graceful-node-shutdown-to-ga.md
rename to content/en/blog/_posts/2023-08-16-non-graceful-node-shutdown-to-ga.md
index 6e5e12ec46..16c2c0550d 100644
--- a/content/en/blog/_posts/2023-08-15-non-graceful-node-shutdown-to-ga.md
+++ b/content/en/blog/_posts/2023-08-16-non-graceful-node-shutdown-to-ga.md
@@ -1,7 +1,7 @@
---
layout: blog
title: "Kubernetes 1.28: Non-Graceful Node Shutdown Moves to GA"
-date: 2023-08-15T10:00:00-08:00
+date: 2023-08-16T10:00:00-08:00
slug: kubernetes-1-28-non-graceful-node-shutdown-GA
---
From fe7759b7347c6f7edbad875239c6710b1ed1465a Mon Sep 17 00:00:00 2001
From: Alex Zielenski
Date: Tue, 8 Aug 2023 13:35:52 -0700
Subject: [PATCH 207/446] ValidatingAdmissionPolicy: add docs for new per
namespace policy params feature (#42219)
* document per namespace params
* switch examples to codenew, fixup some typos
* more formatting and codenew
* use codenew instead of code
* fixup headings
---
.../validating-admission-policy.md | 248 ++++++------------
.../basic-example-binding.yaml | 11 +
.../basic-example-policy.yaml | 14 +
.../binding-with-param-prod.yaml | 17 ++
.../binding-with-param.yaml | 14 +
.../failure-policy-ignore.yaml | 7 +
.../policy-with-param.yaml | 18 ++
.../replicalimit-param-prod.yaml | 5 +
.../replicalimit-param.yaml | 6 +
.../typechecking-multiple-match.yaml | 15 ++
.../typechecking.yaml | 15 ++
11 files changed, 201 insertions(+), 169 deletions(-)
create mode 100644 content/en/examples/validatingadmissionpolicy/basic-example-binding.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/basic-example-policy.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/binding-with-param-prod.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/binding-with-param.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/failure-policy-ignore.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/policy-with-param.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/replicalimit-param-prod.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/replicalimit-param.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/typechecking-multiple-match.yaml
create mode 100644 content/en/examples/validatingadmissionpolicy/typechecking.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 8b743e8e9f..17edf90819 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
@@ -9,7 +9,7 @@ content_type: concept
-{{< feature-state state="alpha" for_k8s_version="v1.26" >}}
+{{< feature-state state="beta" for_k8s_version="v1.28" >}}
This page provides an overview of Validating Admission Policy.
@@ -45,12 +45,12 @@ At least a `ValidatingAdmissionPolicy` and a corresponding `ValidatingAdmission
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.
+`spec.paramKind` in `ValidatingAdmissionPolicy` not specified.
## {{% 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.
+- Ensure that the `admissionregistration.k8s.io/v1beta1` API is enabled.
## Getting Started with Validating Admission Policy
@@ -61,22 +61,7 @@ with great caution. The following describes how to quickly experiment with Valid
The following is an example of a 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"
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/basic-example-policy.yaml" %}}
`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
@@ -85,19 +70,7 @@ 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.:
-```yaml
-apiVersion: admissionregistration.k8s.io/v1alpha1
-kind: ValidatingAdmissionPolicyBinding
-metadata:
- name: "demo-binding-test.example.com"
-spec:
- policyName: "demo-policy.example.com"
- validationActions: [Deny]
- matchResources:
- namespaceSelector:
- matchLabels:
- environment: test
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/basic-example-binding.yaml" %}}
When trying to create a deployment with replicas set not satisfying the validation expression, an
error will return containing message:
@@ -133,13 +106,13 @@ 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),
+according to these actions only if the `failurePolicy` is set to `Fail` (or not specified),
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
Parameter resources allow a policy configuration to be separate from its definition.
A policy can define paramKind, which outlines GVK of the parameter resource,
@@ -148,26 +121,7 @@ and then a policy binding ties a policy by name (via policyName) to a particular
If parameter configuration is needed, the following is an example of a ValidatingAdmissionPolicy
with parameter configuration.
-```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
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/policy-with-param.yaml" %}}
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.
@@ -182,89 +136,51 @@ 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.
+are created. The following is an example of a ValidatingAdmissionPolicyBinding
+that uses a **cluster-wide** param - the same param will be used to validate
+every resource request that matches the binding:
-```yaml
-apiVersion: admissionregistration.k8s.io/v1alpha1
-kind: ValidatingAdmissionPolicyBinding
-metadata:
- name: "replicalimit-binding-test.example.com"
-spec:
- policyName: "replicalimit-policy.example.com"
- validationActions: [Deny]
- paramRef:
- name: "replica-limit-test.example.com"
- matchResources:
- namespaceSelector:
- matchLabels:
- environment: test
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/binding-with-param.yaml" %}}
+
+Notice this binding applies a parameter to the policy for all resources which
+are in the `test` environment.
The parameter resource could be as following:
-```yaml
-apiVersion: rules.example.com/v1
-kind: ReplicaLimit
-metadata:
- name: "replica-limit-test.example.com"
-maxReplicas: 3
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/replicalimit-param.yaml" %}}
-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:
+This policy parameter resource limits deployments to a max of 3 replicas.
-```yaml
-apiVersion: admissionregistration.k8s.io/v1alpha1
-kind: ValidatingAdmissionPolicyBinding
-metadata:
- name: "replicalimit-binding-nontest"
-spec:
- policyName: "replicalimit-policy.example.com"
- validationActions: [Deny]
- paramRef:
- name: "replica-limit-clusterwide.example.com"
- matchResources:
- namespaceSelector:
- matchExpressions:
- - key: environment
- operator: NotIn
- values:
- - test
-```
+An admission policy may have multiple bindings. To bind all other environments
+to have a maxReplicas limit of 100, create another ValidatingAdmissionPolicyBinding:
-And have a parameter resource like:
+{{% codenew language="yaml" file="validatingadmissionpolicy/binding-with-param-prod.yaml" %}}
-```yaml
-apiVersion: rules.example.com/v1
-kind: ReplicaLimit
-metadata:
- name: "replica-limit-clusterwide.example.com"
-maxReplicas: 100
-```
+Notice this binding applies a different parameter to resources which
+are not in the `test` environment.
-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:
+And have a parameter resource:
-```yaml
-apiVersion: admissionregistration.k8s.io/v1alpha1
-kind: ValidatingAdmissionPolicyBinding
-metadata:
- name: "replicalimit-binding-global"
-spec:
- policyName: "replicalimit-policy.example.com"
- validationActions: [Deny]
- params: "replica-limit-clusterwide.example.com"
- matchResources:
- namespaceSelector:
- matchExpressions:
- - key: environment
- operator: Exists
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/replicalimit-param-prod.yaml" %}}
+
+For each admission request, the API server evaluates CEL expressions of each
+(policy, binding, param) combination that match the request. For a request
+to be admitted it must pass **all** evaluations.
+
+If multiple bindings match the request, the policy will be evaluated for each,
+and they must all pass evaluation for the policy to be considered passed.
+
+If multiple parameters match a single binding, the policy rules will be evaluated
+for each param, and they too must all pass for the binding to be considered passed.
+Bindings can have overlapping match criteria. The policy is evaluated for each
+matching binding-parameter combination. A policy may even be evaluated multiple
+times if multiple bindings match it, or a single binding that matches multiple
+parameters.
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.
+ensure one has been bound. A parameter resource will not be bound and `params` will be null
+if `paramKind` of the policy, or `paramRef` of the binding are not specified.
For the use cases require parameter configuration, we recommend to add a param check in
`spec.validations[0].expression`:
@@ -274,6 +190,8 @@ For the use cases require parameter configuration, we recommend to add a param c
message: "params missing but required to bind to this policy"
```
+#### Optional parameters
+
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,
@@ -291,7 +209,38 @@ Here, we first check that the optional parameter is present with `!has(params.op
evaluated, and optionalNumber will be checked to ensure that it contains a value between 5 and
10 inclusive.
-#### Authorization Check
+
+#### Per-namespace Parameters
+
+As the author of a ValidatingAdmissionPolicy and its ValidatingAdmissionPolicyBinding,
+you can choose to specify cluster-wide, or per-namespace parameters.
+If you specify a `namespace` for the binding's `paramRef`, the control plane only
+searches for parameters in that namespace.
+
+However, if `namespace` is not specified in the ValidatingAdmissionPolicyBinding, the
+API server can search for relevant parameters in the namespace that a request is against.
+For example, if you make a request to modify a ConfigMap in the `default` namespace and
+there is a relevant ValidatingAdmissionPolicyBinding with no `namespace` set, then the
+API server looks for a parameter object in `default`.
+This design enables policy configuration that depends on the namespace
+of the resource being manipulated, for more fine-tuned control.
+
+#### Parameter selector
+
+In addition to specify a parameter in a binding by `name`, you may
+choose instead to specify label selector, such that all resources of the
+policy's `paramKind`, and the param's `namespace` (if applicable) that match the
+label selector are selected for evaluation. See {{< glossary_tooltip text="selector" term_id="selector">}} for more information on how label selectors match resources.
+
+If multiple parameters are found to meet the condition, the policy's rules are
+evaluated for each parameter found and the results will be ANDed together.
+
+If `namespace` is provided, only objects of the `paramKind` in the provided
+namespace are eligible for selection. Otherwise, when `namespace` is empty and
+`paramKind` is namespace-scoped, the `namespace` used in the request being
+admitted will be used.
+
+#### Authorization checks {#authorization-check}
We introduced the authorization check for parameter resources.
User is expected to have `read` access to the resources referenced by `paramKind` in
@@ -312,15 +261,7 @@ admission policy are handled. Allowed values are `Ignore` or `Fail`.
Note that the `failurePolicy` is defined inside `ValidatingAdmissionPolicy`:
-```yaml
-apiVersion: admissionregistration.k8s.io/v1alpha1
-kind: ValidatingAdmissionPolicy
-spec:
-...
-failurePolicy: Ignore # The default is "Fail"
-validations:
-- expression: "object.spec.xyz == params.x"
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/failure-policy-ignore.yaml" %}}
### Validation Expression
@@ -333,7 +274,7 @@ variables as well as some other useful variables:
- '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.
+ null if `ParamKind` is not specified.
- `namespaceObject` - The namespace, as a Kubernetes resource, that the incoming object belongs to.
The value is null if the incoming object is cluster-scoped.
- `authorizer` - A CEL Authorizer. May be used to perform authorization checks for the principal
@@ -503,23 +444,7 @@ 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
-```
+{{< codenew language="yaml" file="validatingadmissionpolicy/typechecking.yaml" >}}
The status will yield the following information:
@@ -537,23 +462,8 @@ status:
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
-```
+{{% codenew language="yaml" file="validatingadmissionpolicy/typechecking-multiple-match.yaml" %}}
+
will have multiple types and type checking result of each type in the warning message.
diff --git a/content/en/examples/validatingadmissionpolicy/basic-example-binding.yaml b/content/en/examples/validatingadmissionpolicy/basic-example-binding.yaml
new file mode 100644
index 0000000000..54b7679aaf
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/basic-example-binding.yaml
@@ -0,0 +1,11 @@
+apiVersion: admissionregistration.k8s.io/v1alpha1
+kind: ValidatingAdmissionPolicyBinding
+metadata:
+ name: "demo-binding-test.example.com"
+spec:
+ policyName: "demo-policy.example.com"
+ validationActions: [Deny]
+ matchResources:
+ namespaceSelector:
+ matchLabels:
+ environment: test
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/basic-example-policy.yaml b/content/en/examples/validatingadmissionpolicy/basic-example-policy.yaml
new file mode 100644
index 0000000000..bfdb9ee214
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/basic-example-policy.yaml
@@ -0,0 +1,14 @@
+apiVersion: admissionregistration.k8s.io/v1beta1
+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"
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/binding-with-param-prod.yaml b/content/en/examples/validatingadmissionpolicy/binding-with-param-prod.yaml
new file mode 100644
index 0000000000..a2186ee862
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/binding-with-param-prod.yaml
@@ -0,0 +1,17 @@
+apiVersion: admissionregistration.k8s.io/v1beta1
+kind: ValidatingAdmissionPolicyBinding
+metadata:
+ name: "replicalimit-binding-nontest"
+spec:
+ policyName: "replicalimit-policy.example.com"
+ validationActions: [Deny]
+ paramRef:
+ name: "replica-limit-prod.example.com"
+ namespace: "default"
+ matchResources:
+ namespaceSelector:
+ matchExpressions:
+ - key: environment
+ operator: NotIn
+ values:
+ - test
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/binding-with-param.yaml b/content/en/examples/validatingadmissionpolicy/binding-with-param.yaml
new file mode 100644
index 0000000000..cad7a5b02f
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/binding-with-param.yaml
@@ -0,0 +1,14 @@
+apiVersion: admissionregistration.k8s.io/v1beta1
+kind: ValidatingAdmissionPolicyBinding
+metadata:
+ name: "replicalimit-binding-test.example.com"
+spec:
+ policyName: "replicalimit-policy.example.com"
+ validationActions: [Deny]
+ paramRef:
+ name: "replica-limit-test.example.com"
+ namespace: "default"
+ matchResources:
+ namespaceSelector:
+ matchLabels:
+ environment: test
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/failure-policy-ignore.yaml b/content/en/examples/validatingadmissionpolicy/failure-policy-ignore.yaml
new file mode 100644
index 0000000000..53e3990a1f
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/failure-policy-ignore.yaml
@@ -0,0 +1,7 @@
+apiVersion: admissionregistration.k8s.io/v1beta1
+kind: ValidatingAdmissionPolicy
+spec:
+...
+failurePolicy: Ignore # The default is "Fail"
+validations:
+- expression: "object.spec.xyz == params.x"
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/policy-with-param.yaml b/content/en/examples/validatingadmissionpolicy/policy-with-param.yaml
new file mode 100644
index 0000000000..c493115987
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/policy-with-param.yaml
@@ -0,0 +1,18 @@
+apiVersion: admissionregistration.k8s.io/v1beta1
+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
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/replicalimit-param-prod.yaml b/content/en/examples/validatingadmissionpolicy/replicalimit-param-prod.yaml
new file mode 100644
index 0000000000..ba1832d16a
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/replicalimit-param-prod.yaml
@@ -0,0 +1,5 @@
+apiVersion: rules.example.com/v1
+kind: ReplicaLimit
+metadata:
+ name: "replica-limit-prod.example.com"
+maxReplicas: 100
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/replicalimit-param.yaml b/content/en/examples/validatingadmissionpolicy/replicalimit-param.yaml
new file mode 100644
index 0000000000..813bc7b334
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/replicalimit-param.yaml
@@ -0,0 +1,6 @@
+apiVersion: rules.example.com/v1
+kind: ReplicaLimit
+metadata:
+ name: "replica-limit-test.example.com"
+ namesapce: "default"
+maxReplicas: 3
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/typechecking-multiple-match.yaml b/content/en/examples/validatingadmissionpolicy/typechecking-multiple-match.yaml
new file mode 100644
index 0000000000..77a49d192c
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/typechecking-multiple-match.yaml
@@ -0,0 +1,15 @@
+apiVersion: admissionregistration.k8s.io/v1beta1
+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
\ No newline at end of file
diff --git a/content/en/examples/validatingadmissionpolicy/typechecking.yaml b/content/en/examples/validatingadmissionpolicy/typechecking.yaml
new file mode 100644
index 0000000000..f088420811
--- /dev/null
+++ b/content/en/examples/validatingadmissionpolicy/typechecking.yaml
@@ -0,0 +1,15 @@
+apiVersion: admissionregistration.k8s.io/v1beta1
+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
\ No newline at end of file
From 2ed54d6ebb4d5a3242af129cc547cee6260b9883 Mon Sep 17 00:00:00 2001
From: Arhell
Date: Wed, 9 Aug 2023 00:45:48 +0300
Subject: [PATCH 208/446] [pt] attached correct link
---
content/pt-br/docs/concepts/security/overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt-br/docs/concepts/security/overview.md b/content/pt-br/docs/concepts/security/overview.md
index 6203d6f949..12844b5dc3 100644
--- a/content/pt-br/docs/concepts/security/overview.md
+++ b/content/pt-br/docs/concepts/security/overview.md
@@ -53,7 +53,7 @@ Provedor IaaS | Link |
Alibaba Cloud | https://www.alibabacloud.com/trust-center |
Amazon Web Services | https://aws.amazon.com/security/ |
Google Cloud Platform | https://cloud.google.com/security/ |
-Huawei Cloud | https://www.huaweicloud.com/securecenter/overallsafety.html |
+Huawei Cloud | https://www.huaweicloud.com/intl/pt-br/securecenter/overallsafety |
IBM Cloud | https://www.ibm.com/cloud/security |
Microsoft Azure | https://docs.microsoft.com/en-us/azure/security/azure-security |
Oracle Cloud Infrastructure | https://www.oracle.com/security/ |
From b75a6a531b94e3aea50cddd08bc69ce85d95d401 Mon Sep 17 00:00:00 2001
From: Rishit Dagli
Date: Tue, 8 Aug 2023 19:40:54 -0400
Subject: [PATCH 209/446] Update hugo.toml for 1.28
---
hugo.toml | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/hugo.toml b/hugo.toml
index 87fe123737..88cdfc3648 100644
--- a/hugo.toml
+++ b/hugo.toml
@@ -191,34 +191,34 @@ docsbranch = "main"
url = "https://kubernetes.io"
[[params.versions]]
-fullversion = "v1.27.0" # legacy; use {{< skew currentPatchVersion >}} instead
+fullversion = "v1.27.4" # legacy; use {{< skew currentPatchVersion >}} instead
# retain until all localizations have migrated
version = "v1.27"
-githubbranch = "v1.27.0"
+githubbranch = "v1.27.4"
docsbranch = "release-1.27"
url = "https://v1-27.docs.kubernetes.io"
[[params.versions]]
-fullversion = "v1.26.3" # legacy; use {{< skew currentPatchVersion >}} instead
+fullversion = "v1.26.7" # legacy; use {{< skew currentPatchVersion >}} instead
# retain until all localizations have migrated
version = "v1.26"
-githubbranch = "v1.26.3"
+githubbranch = "v1.26.7"
docsbranch = "release-1.26"
url = "https://v1-26.docs.kubernetes.io"
[[params.versions]]
-fullversion = "v1.25.8" # legacy; use {{< skew currentPatchVersion >}} instead
+fullversion = "v1.25.12" # legacy; use {{< skew currentPatchVersion >}} instead
# retain until all localizations have migrated
version = "v1.25"
-githubbranch = "v1.25.8"
+githubbranch = "v1.25.12"
docsbranch = "release-1.25"
url = "https://v1-25.docs.kubernetes.io"
[[params.versions]]
-fullversion = "v1.24.12" # legacy; use {{< skew currentPatchVersion >}} instead
+fullversion = "v1.24.16" # legacy; use {{< skew currentPatchVersion >}} instead
# retain until all localizations have migrated
version = "v1.24"
-githubbranch = "v1.24.12"
+githubbranch = "v1.24.16"
docsbranch = "release-1.24"
url = "https://v1-24.docs.kubernetes.io"
From 77afa1f57b57b348baba803f178fa4b3b97908e0 Mon Sep 17 00:00:00 2001
From: windsonsea
Date: Wed, 9 Aug 2023 08:57:38 +0800
Subject: [PATCH 210/446] [zh] sync pods-and-endpoint-termination-flow.md
---
.../services/connect-applications-service.md | 19 ++++--
.../pods-and-endpoint-termination-flow.md | 60 +++----------------
.../docs/tutorials/services/source-ip.md | 27 ++++++++-
.../explore-graceful-termination-nginx.yaml | 11 ++++
4 files changed, 59 insertions(+), 58 deletions(-)
create mode 100644 content/zh-cn/examples/service/explore-graceful-termination-nginx.yaml
diff --git a/content/zh-cn/docs/tutorials/services/connect-applications-service.md b/content/zh-cn/docs/tutorials/services/connect-applications-service.md
index 57bb46162f..1be3682f11 100644
--- a/content/zh-cn/docs/tutorials/services/connect-applications-service.md
+++ b/content/zh-cn/docs/tutorials/services/connect-applications-service.md
@@ -55,7 +55,7 @@ Create an nginx Pod, and note that it has a container port specification:
我们在之前的示例中已经做过,然而让我们以网络连接的视角再重做一遍。
创建一个 Nginx Pod,注意其中包含一个容器端口的规约:
-{{< codenew file="service/networking/run-my-nginx.yaml" >}}
+{{< code file="service/networking/run-my-nginx.yaml" >}}
这等价于使用 `kubectl create -f` 命令及如下的 yaml 文件创建:
-{{< codenew file="service/networking/nginx-svc.yaml" >}}
+{{< code file="service/networking/nginx-svc.yaml" >}}
以下是你在运行 make 时遇到问题时要遵循的手动步骤(例如,在 Windows 上):
+
```shell
# 创建公钥和相对应的私钥
openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /d/tmp/nginx.key -out /d/tmp/nginx.crt -subj "/CN=my-nginx/O=my-nginx"
@@ -461,7 +470,7 @@ cat /d/tmp/nginx.key | base64
Use the output from the previous commands to create a yaml file as follows.
The base64 encoded value should all be on a single line.
-->
-使用前面命令的输出来创建 yaml 文件,如下所示。 base64 编码的值应全部放在一行上。
+如下所示,使用上述命令的输出来创建 yaml 文件。base64 编码的值应全部放在一行上。
```yaml
apiVersion: "v1"
@@ -495,7 +504,7 @@ in the secret, and the Service, to expose both ports (80 and 443):
-->
现在修改 Nginx 副本以启动一个使用 Secret 中的证书的 HTTPS 服务器以及相应的用于暴露其端口(80 和 443)的 Service:
-{{< codenew file="service/networking/nginx-secure-app.yaml" >}}
+{{< code file="service/networking/nginx-secure-app.yaml" >}}
-```yaml
-apiVersion: apps/v1
-kind: Deployment
-metadata:
- name: nginx-deployment
- labels:
- app: nginx
-spec:
- replicas: 1
- selector:
- matchLabels:
- app: nginx
- template:
- metadata:
- labels:
- app: nginx
- spec:
- terminationGracePeriodSeconds: 120 # 超长优雅期
- containers:
- - name: nginx
- image: nginx:latest
- ports:
- - containerPort: 80
- lifecycle:
- preStop:
- exec:
- # 实际生产环境中的 Pod 终止可能需要执行任何时长,但不会超过 terminationGracePeriodSeconds。
- # 在本例中,只需挂起至少 terminationGracePeriodSeconds 所指定的持续时间,
- # 在 120 秒时容器将被强制终止。
- # 请注意,在所有这些时间点 nginx 都将继续处理请求。
- command: [
- "/bin/sh", "-c", "sleep 180"
- ]
+现在使用以上文件创建 Deployment Pod 和 Service:
----
-
-apiVersion: v1
-kind: Service
-metadata:
- name: nginx-service
-spec:
- selector:
- app: nginx
- ports:
- - protocol: TCP
- port: 80
- targetPort: 80
+```shell
+kubectl apply -f pod-with-graceful-termination.yaml
+kubectl apply -f explore-graceful-termination-nginx.yaml
```
@@ -222,6 +223,7 @@ You can then run a command inside that Pod:
# 从 “kubectl run” 的终端中运行
ip addr
```
+
```
1: lo: mtu 65536 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
@@ -303,6 +305,7 @@ port allocated above.
```shell
for node in $NODES; do curl -s $node:$NODEPORT | grep -i client_address; done
```
+
@@ -386,6 +389,7 @@ for node in $NODES; do curl --connect-timeout 1 -s $node:$NODEPORT | grep -i cli
The output is similar to:
-->
输出类似于:
+
```
client_address=198.51.100.79
```
@@ -447,6 +451,7 @@ kubectl expose deployment source-ip-app --name=loadbalancer --port=80 --target-p
The output is:
-->
输出为:
+
```
service/loadbalancer exposed
```
@@ -455,13 +460,16 @@ service/loadbalancer exposed
Print out the IP addresses of the Service:
-->
打印 Service 的 IP 地址:
+
```console
kubectl get svc loadbalancer
```
+
输出类似于:
+
```
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
loadbalancer LoadBalancer 10.0.65.118 203.0.113.140 80/TCP 5m
@@ -471,13 +479,16 @@ loadbalancer LoadBalancer 10.0.65.118 203.0.113.140 80/TCP 5m
Next, send a request to this Service's external-ip:
-->
接下来,发送请求到 Service 的 的外部 IP(External-IP):
+
```shell
curl 203.0.113.140
```
+
输出类似于:
+
```
CLIENT VALUES:
client_address=10.240.0.5
@@ -524,6 +535,7 @@ kubectl get svc loadbalancer -o yaml | grep -i healthCheckNodePort
The output is similar to this:
-->
输出类似于:
+
```yaml
healthCheckNodePort: 32122
```
@@ -542,6 +554,7 @@ kubectl get pod -o wide -l app=source-ip-app
The output is similar to this:
-->
输出类似于:
+
```
NAME READY STATUS RESTARTS AGE IP NODE
source-ip-app-826191075-qehz4 1/1 Running 0 20h 10.180.1.136 kubernetes-node-6jst
@@ -551,10 +564,15 @@ source-ip-app-826191075-qehz4 1/1 Running 0 20h 10.180.
Use `curl` to fetch the `/healthz` endpoint on various nodes:
-->
使用 `curl` 获取各个节点上的 `/healthz` 端点:
+
+
```shell
# 在你选择的节点上本地运行
curl localhost:32122/healthz
```
+
```
1 Service Endpoints found
```
@@ -563,10 +581,15 @@ curl localhost:32122/healthz
On a different node you might get a different result:
-->
在不同的节点上,你可能会得到不同的结果:
+
+
```shell
# 在你选择的节点上本地运行
curl localhost:32122/healthz
```
+
```
No Service Endpoints Found
```
@@ -586,10 +609,12 @@ then use `curl` to query the IPv4 address of the load balancer:
```shell
curl 203.0.113.140
```
+
输出类似于:
+
```
CLIENT VALUES:
client_address=198.51.100.79
diff --git a/content/zh-cn/examples/service/explore-graceful-termination-nginx.yaml b/content/zh-cn/examples/service/explore-graceful-termination-nginx.yaml
new file mode 100644
index 0000000000..6d1f97a64d
--- /dev/null
+++ b/content/zh-cn/examples/service/explore-graceful-termination-nginx.yaml
@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: Service
+metadata:
+ name: nginx-service
+spec:
+ selector:
+ app: nginx
+ ports:
+ - protocol: TCP
+ port: 80
+ targetPort: 80
\ No newline at end of file
From 690fd456443da23dfe3836d5a96937df2a0fae84 Mon Sep 17 00:00:00 2001
From: windsonsea
Date: Wed, 9 Aug 2023 09:16:42 +0800
Subject: [PATCH 211/446] use a consistent code reference in
pods-and-endpoint-termination-flow
---
.../tutorials/services/pods-and-endpoint-termination-flow.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md b/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md
index a2757bdd89..d056b62e53 100644
--- a/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md
+++ b/content/en/docs/tutorials/services/pods-and-endpoint-termination-flow.md
@@ -38,7 +38,7 @@ Let's say you have a Deployment containing of a single `nginx` replica
{{% code file="service/pod-with-graceful-termination.yaml" %}}
-{{< codenew file="service/explore-graceful-termination-nginx.yaml" >}}
+{{% code file="service/explore-graceful-termination-nginx.yaml" %}}
Now create the Deployment Pod and Service using the above files:
From 42078a08fb20073b84edd0b96d7ef8a987e5fce1 Mon Sep 17 00:00:00 2001
From: Amine
Date: Tue, 8 Aug 2023 20:21:19 +0200
Subject: [PATCH 212/446] Fix typos and add comments to the match conditions
example
---
.../access-authn-authz/extensible-admission-controllers.md | 4 ++--
.../validating-webhook-configuration-match-conditions.yaml | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
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 7f6cdc04df..a2d199392a 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
@@ -723,7 +723,7 @@ The `matchPolicy` for an admission webhooks defaults to `Equivalent`.
{{< feature-state state="beta" for_k8s_version="v1.28" >}}
-You can define _match conditions_for webhooks if you need fine-grained request filtering. These
+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
@@ -734,7 +734,7 @@ Here is an example illustrating a few different uses for match conditions:
{{< codenew file="access/validating-webhook-configuration-match-conditions.yaml" >}}
{{< note >}}
-You can define up to 64 elements in the `matchConditions`` field per webhook.
+You can define up to 64 elements in the `matchConditions` field per webhook.
{{< /note >}}
Match conditions have access to the following CEL variables:
diff --git a/content/en/examples/access/validating-webhook-configuration-match-conditions.yaml b/content/en/examples/access/validating-webhook-configuration-match-conditions.yaml
index f9a3b25624..37d12f22f1 100644
--- a/content/en/examples/access/validating-webhook-configuration-match-conditions.yaml
+++ b/content/en/examples/access/validating-webhook-configuration-match-conditions.yaml
@@ -15,6 +15,7 @@ webhooks:
namespace: my-namespace
name: my-webhook
caBundle: ''
+ # You can have up to 64 matchConditions per webhook
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.
@@ -40,6 +41,7 @@ webhooks:
namespace: my-namespace
name: my-webhook
caBundle: ''
+ # You can have up to 64 matchConditions per webhook
matchConditions:
- name: 'breakglass'
# Skip requests made by users authorized to 'breakglass' on this webhook.
From 280583924915af2e52a257c8d284aa9b6a78406e Mon Sep 17 00:00:00 2001
From: Tim Bannister
Date: Wed, 9 Aug 2023 08:53:15 +0100
Subject: [PATCH 213/446] Stop setting deprecated fullversion param
A new shortcode looks up the correct patch version from data maintained
by the release team.
---
hugo.toml | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/hugo.toml b/hugo.toml
index 43503425e2..c68ebc1bfc 100644
--- a/hugo.toml
+++ b/hugo.toml
@@ -140,9 +140,6 @@ showedit = true
latest = "v1.27"
-fullversion = "v1.27.0" # legacy; use {{< skew currentPatchVersion >}} instead
- # retain until all localizations have migrated
-
version = "v1.27"
githubbranch = "main"
docsbranch = "main"
@@ -183,40 +180,30 @@ js = [
]
[[params.versions]]
-fullversion = "v1.27.0" # legacy; use {{< skew currentPatchVersion >}} instead
- # retain until all localizations have migrated
version = "v1.27"
githubbranch = "v1.27.0"
docsbranch = "main"
url = "https://kubernetes.io"
[[params.versions]]
-fullversion = "v1.26.3" # legacy; use {{< skew currentPatchVersion >}} instead
- # retain until all localizations have migrated
version = "v1.26"
githubbranch = "v1.26.3"
docsbranch = "release-1.26"
url = "https://v1-26.docs.kubernetes.io"
[[params.versions]]
-fullversion = "v1.25.8" # legacy; use {{< skew currentPatchVersion >}} instead
- # retain until all localizations have migrated
version = "v1.25"
githubbranch = "v1.25.8"
docsbranch = "release-1.25"
url = "https://v1-25.docs.kubernetes.io"
[[params.versions]]
-fullversion = "v1.24.12" # legacy; use {{< skew currentPatchVersion >}} instead
- # retain until all localizations have migrated
version = "v1.24"
githubbranch = "v1.24.12"
docsbranch = "release-1.24"
url = "https://v1-24.docs.kubernetes.io"
[[params.versions]]
-fullversion = "v1.23.17" # legacy; use {{< skew currentPatchVersion >}} instead
- # retain until all localizations have migrated
version = "v1.23"
githubbranch = "v1.23.17"
docsbranch = "release-1.23"
From 2fbf0490e2e52a8d9a554e9b807b0654d105c880 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 9 Aug 2023 16:43:18 +0800
Subject: [PATCH 214/446] sync horizontal-pod-autoscale-walkthrough
run-stateless-application-deployment install-kubectl-linux
---
.../run-application/horizontal-pod-autoscale-walkthrough.md | 4 ++--
.../run-application/run-stateless-application-deployment.md | 6 +++---
content/zh-cn/docs/tasks/tools/install-kubectl-linux.md | 5 ++---
3 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
index e32d32fac7..9398388183 100644
--- a/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+++ b/content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
@@ -104,7 +104,7 @@ using the following manifest:
为了演示 HorizontalPodAutoscaler,你将首先启动一个 Deployment 用 `hpa-example` 镜像运行一个容器,
然后使用以下清单文件将其暴露为一个 {{< glossary_tooltip term_id="service">}}:
-{{% codenew file="application/php-apache.yaml" %}}
+{{% code file="application/php-apache.yaml" %}}
除了使用 `kubectl autoscale` 命令,也可以使用以下清单以声明方式创建 HorizontalPodAutoscaler:
-{{% codenew file="application/hpa/php-apache.yaml" %}}
+{{% code file="application/hpa/php-apache.yaml" %}}
在低于 Debian 12 和 Ubuntu 22.04 的发行版本中,`/etc/apt/keyrings` 默认不存在。
-如有需要,你可以创建此目录,并将其设置为对所有人可读,但仅对管理员可写。
+可以使用 `sudo mkdir -m 755 /etc/apt/keyrings` 来创建。
{{< /note >}}
{{% /tab %}}
From de8c9692410522c4b48825e82eb0cb0bee3209ad Mon Sep 17 00:00:00 2001
From: Matthias Bertschy
Date: Tue, 8 Aug 2023 11:53:36 +0200
Subject: [PATCH 215/446] nit edits for Sidecar containers
Signed-off-by: Matthias Bertschy
---
content/en/docs/concepts/workloads/pods/_index.md | 5 +++--
.../en/docs/concepts/workloads/pods/init-containers.md | 10 ++++++----
2 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/content/en/docs/concepts/workloads/pods/_index.md b/content/en/docs/concepts/workloads/pods/_index.md
index 19f2564c30..798b7926a5 100644
--- a/content/en/docs/concepts/workloads/pods/_index.md
+++ b/content/en/docs/concepts/workloads/pods/_index.md
@@ -118,8 +118,9 @@ By default, init containers run and complete before the app containers are start
{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
-Enabling the [SidecarContainers feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-allows specifying a restartPolicy=Always to init containers, making sure they are
+Enabling the `SidecarContainers` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+allows you to specify `restartPolicy: Always` for init containers.
+Setting the `Always` restart policy ensures that the init containers where you set it are
kept running during the entire lifetime of the Pod.
See [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/init-containers/#sidecar-containers-and-restartpolicy)
for more details.
diff --git a/content/en/docs/concepts/workloads/pods/init-containers.md b/content/en/docs/concepts/workloads/pods/init-containers.md
index e0e5f26fce..83ccab4cd5 100644
--- a/content/en/docs/concepts/workloads/pods/init-containers.md
+++ b/content/en/docs/concepts/workloads/pods/init-containers.md
@@ -294,7 +294,7 @@ validation error is thrown for any container sharing a name with another.
{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
Starting with Kubernetes 1.28 in alpha, a feature gate named `SidecarContainers`
-allows to specify a `restartPolicy` for init containers which is independent of
+allows you to specify a `restartPolicy` for init containers which is independent of
the Pod and other init containers. Container [probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe)
can also be added to control their lifecycle.
@@ -309,9 +309,11 @@ Since these containers are defined as init containers, they benefit from the sam
ordering and sequential guarantees as other init containers, allowing them to
be mixed with other init containers into complex Pod initialization flows.
-The only difference is that they are not required to complete before the next
-init container starts, so a next init container will start after the current
-container status has been set to `Pod.status.containerStatuses[id of container].started=true`
+Compared to regular init containers, sidecar-style init containers continue to
+run and the next init container can begin starting once the kubelet has set
+the `started` container status for the sidecar-style init container to true.
+That status either becomes true because there is a process running in the
+container and no startup probe defined, or
as a result of its `startupProbe` succeeding.
This feature can be used to implement the sidecar container pattern in a more
From dc84936a0064ea8063abb298ee2982ca32552b0e Mon Sep 17 00:00:00 2001
From: Roman Bednar
Date: Wed, 2 Aug 2023 11:54:58 +0200
Subject: [PATCH 216/446] add blog for Retroactive Default StorageClass move to
GA
---
...18-retroactive-default-storage-class-ga.md | 39 +++++++++++++++++++
1 file changed, 39 insertions(+)
create mode 100644 content/en/blog/_posts/2023-08-18-retroactive-default-storage-class-ga.md
diff --git a/content/en/blog/_posts/2023-08-18-retroactive-default-storage-class-ga.md b/content/en/blog/_posts/2023-08-18-retroactive-default-storage-class-ga.md
new file mode 100644
index 0000000000..1645521152
--- /dev/null
+++ b/content/en/blog/_posts/2023-08-18-retroactive-default-storage-class-ga.md
@@ -0,0 +1,39 @@
+---
+layout: blog
+title: "Kubernetes v1.28: Retroactive Default StorageClass move to GA"
+date: 2023-08-18
+slug: retroactive-default-storage-class-ga
+---
+
+**Author:** Roman Bednář (Red Hat)
+
+Announcing graduation to General Availability (GA) - Retroactive Default StorageClass Assignment in Kubernetes v1.28!
+
+Kubernetes SIG Storage team is thrilled to announce that the "Retroactive Default StorageClass Assignment" feature,
+introduced as an alpha in Kubernetes v1.25, has now graduated to GA and is officially part of the Kubernetes v1.28 release.
+This enhancement brings a significant improvement to how default
+[StorageClasses](/docs/concepts/storage/storage-classes/) are assigned to PersistentVolumeClaims (PVCs).
+
+With this feature enabled, you no longer need to create a default StorageClass first and then a PVC to assign the class.
+Instead, any PVCs without a StorageClass assigned will now be retroactively updated to include the default StorageClass.
+This enhancement ensures that PVCs no longer get stuck in an unbound state, and storage provisioning works seamlessly,
+even when a default StorageClass is not defined at the time of PVC creation.
+
+## What changed?
+
+The PersistentVolume (PV) controller has been modified to automatically assign a default StorageClass to any unbound
+PersistentVolumeClaim with the `storageClassName` not set. Additionally, the PersistentVolumeClaim
+admission validation mechanism within
+the API server has been adjusted to allow changing values from an unset state to an actual StorageClass name.
+
+## How to use it?
+
+As this feature has graduated to GA, there's no need to enable a feature gate anymore.
+Simply make sure you are running Kubernetes v1.28 or later, and the feature will be available for use.
+
+For more details, read about
+[default StorageClass assignment](/docs/concepts/storage/persistent-volumes/#retroactive-default-storageclass-assignment) in the Kubernetes documentation.
+You can also read the previous [blog post](/blog/2023/01/05/retroactive-default-storage-class/) announcing beta graduation in v1.26.
+
+To provide feedback, join our [Kubernetes Storage Special-Interest-Group](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG)
+or participate in discussions on our [public Slack channel](https://app.slack.com/client/T09NY5SBT/C09QZFCE5).
From 9520b96a6162d4af841da63227d2a8710596b975 Mon Sep 17 00:00:00 2001
From: Tim Bannister
Date: Wed, 12 Jul 2023 01:25:31 +0100
Subject: [PATCH 217/446] Revise docs home page
Reorder and replace cards to better (I hope!) serve our readers.
---
.../docs/concepts/cluster-administration/_index.md | 6 ++++++
content/en/docs/concepts/containers/_index.md | 3 +++
content/en/docs/concepts/overview/_index.md | 3 +++
content/en/docs/concepts/overview/components.md | 1 +
content/en/docs/concepts/workloads/_index.md | 4 ++++
content/en/docs/concepts/workloads/pods/_index.md | 3 ---
.../en/docs/contribute/style/page-content-types.md | 3 ---
.../en/docs/contribute/suggesting-improvements.md | 5 ++++-
content/en/docs/home/_index.md | 14 +++++++-------
content/en/docs/reference/kubectl/_index.md | 1 +
content/en/docs/reference/kubectl/cheatsheet.md | 4 ++--
content/en/docs/reference/kubernetes-api/_index.md | 4 ++++
.../reference/labels-annotations-taints/_index.md | 6 ++++++
.../docs/reference/setup-tools/kubeadm/_index.md | 5 +++--
.../tools/kubeadm/install-kubeadm.md | 2 +-
.../configure-access-multiple-clusters.md | 3 ++-
content/en/docs/tasks/debug/_index.md | 4 ++++
content/en/docs/tasks/tools/_index.md | 6 ++++++
.../en/docs/tasks/tools/install-kubectl-linux.md | 4 ----
.../en/docs/tasks/tools/install-kubectl-macos.md | 4 ----
.../en/docs/tasks/tools/install-kubectl-windows.md | 4 ----
21 files changed, 57 insertions(+), 32 deletions(-)
diff --git a/content/en/docs/concepts/cluster-administration/_index.md b/content/en/docs/concepts/cluster-administration/_index.md
index d5d6a273e2..2c7baf1d98 100644
--- a/content/en/docs/concepts/cluster-administration/_index.md
+++ b/content/en/docs/concepts/cluster-administration/_index.md
@@ -8,6 +8,12 @@ content_type: concept
description: >
Lower-level detail relevant to creating or administering a Kubernetes cluster.
no_list: true
+card:
+ name: setup
+ weight: 60
+ anchors:
+ - anchor: "#securing-a-cluster"
+ title: Securing a cluster
---
diff --git a/content/en/docs/concepts/containers/_index.md b/content/en/docs/concepts/containers/_index.md
index 8c4316cd64..bb98df7aca 100644
--- a/content/en/docs/concepts/containers/_index.md
+++ b/content/en/docs/concepts/containers/_index.md
@@ -6,6 +6,9 @@ reviewers:
- erictune
- thockin
content_type: concept
+card:
+ name: concepts
+ weight: 50
---
diff --git a/content/en/docs/concepts/overview/_index.md b/content/en/docs/concepts/overview/_index.md
index f5952d39b7..200b3e2ea3 100644
--- a/content/en/docs/concepts/overview/_index.md
+++ b/content/en/docs/concepts/overview/_index.md
@@ -10,6 +10,9 @@ weight: 20
card:
name: concepts
weight: 10
+ anchors:
+ - anchor: "#why-you-need-kubernetes-and-what-can-it-do"
+ title: Why Kubernetes?
no_list: true
---
diff --git a/content/en/docs/concepts/overview/components.md b/content/en/docs/concepts/overview/components.md
index 2c422fcdaa..659592cc6c 100644
--- a/content/en/docs/concepts/overview/components.md
+++ b/content/en/docs/concepts/overview/components.md
@@ -8,6 +8,7 @@ description: >
plane and a set of machines called nodes.
weight: 30
card:
+ title: Components of a cluster
name: concepts
weight: 20
---
diff --git a/content/en/docs/concepts/workloads/_index.md b/content/en/docs/concepts/workloads/_index.md
index 8ae7df3fdb..3fd2a86fc5 100644
--- a/content/en/docs/concepts/workloads/_index.md
+++ b/content/en/docs/concepts/workloads/_index.md
@@ -4,6 +4,10 @@ weight: 55
description: >
Understand Pods, the smallest deployable compute object in Kubernetes, and the higher-level abstractions that help you to run them.
no_list: true
+card:
+ title: Workloads and Pods
+ name: concepts
+ weight: 60
---
{{< glossary_definition term_id="workload" length="short" >}}
diff --git a/content/en/docs/concepts/workloads/pods/_index.md b/content/en/docs/concepts/workloads/pods/_index.md
index ba4b9d47fc..09daed5c25 100644
--- a/content/en/docs/concepts/workloads/pods/_index.md
+++ b/content/en/docs/concepts/workloads/pods/_index.md
@@ -5,9 +5,6 @@ title: Pods
content_type: concept
weight: 10
no_list: true
-card:
- name: concepts
- weight: 60
---
diff --git a/content/en/docs/contribute/style/page-content-types.md b/content/en/docs/contribute/style/page-content-types.md
index bc44c655d1..ada2274d99 100644
--- a/content/en/docs/contribute/style/page-content-types.md
+++ b/content/en/docs/contribute/style/page-content-types.md
@@ -2,9 +2,6 @@
title: Page content types
content_type: concept
weight: 80
-card:
- name: contribute
- weight: 30
---
diff --git a/content/en/docs/contribute/suggesting-improvements.md b/content/en/docs/contribute/suggesting-improvements.md
index d79df11476..aac6ce1c13 100644
--- a/content/en/docs/contribute/suggesting-improvements.md
+++ b/content/en/docs/contribute/suggesting-improvements.md
@@ -4,7 +4,10 @@ content_type: concept
weight: 10
card:
name: contribute
- weight: 20
+ weight: 15
+ anchors:
+ - anchor: "#opening-an-issue"
+ title: Suggest content improvements
---
diff --git a/content/en/docs/home/_index.md b/content/en/docs/home/_index.md
index a580c9aead..c22ec2e8dc 100644
--- a/content/en/docs/home/_index.md
+++ b/content/en/docs/home/_index.md
@@ -41,20 +41,20 @@ cards:
description: "Look up common tasks and how to perform them using a short sequence of steps."
button: "View Tasks"
button_path: "/docs/tasks"
-- name: training
- title: "Training"
- description: "Get certified in Kubernetes and make your cloud native projects successful!"
- button: "View training"
- button_path: "/training"
- name: reference
title: Look up reference information
description: Browse terminology, command line syntax, API resource types, and setup tool documentation.
button: View Reference
button_path: /docs/reference
+- name: training
+ title: "Training"
+ description: "Get certified in Kubernetes and make your cloud native projects successful!"
+ button: "View training"
+ button_path: "/training"
- name: contribute
- title: Contribute to the docs
+ title: Contribute to Kubernetes
description: Anyone can contribute, whether you're new to the project or you've been around a long time.
- button: Contribute to the docs
+ button: Find out how to help
button_path: /docs/contribute
- name: Download
title: Download Kubernetes
diff --git a/content/en/docs/reference/kubectl/_index.md b/content/en/docs/reference/kubectl/_index.md
index 6d72bd0579..6f71573ea0 100644
--- a/content/en/docs/reference/kubectl/_index.md
+++ b/content/en/docs/reference/kubectl/_index.md
@@ -5,6 +5,7 @@ weight: 110
no_list: true
card:
name: reference
+ title: kubectl command line tool
weight: 20
---
diff --git a/content/en/docs/reference/kubectl/cheatsheet.md b/content/en/docs/reference/kubectl/cheatsheet.md
index bbea74d46a..c8bd0ec8f1 100644
--- a/content/en/docs/reference/kubectl/cheatsheet.md
+++ b/content/en/docs/reference/kubectl/cheatsheet.md
@@ -7,8 +7,8 @@ reviewers:
content_type: concept
weight: 10 # highlight it
card:
- name: reference
- weight: 30
+ name: tasks
+ weight: 10
---
diff --git a/content/en/docs/reference/kubernetes-api/_index.md b/content/en/docs/reference/kubernetes-api/_index.md
index 3fd611b1cf..be3b46b9a4 100644
--- a/content/en/docs/reference/kubernetes-api/_index.md
+++ b/content/en/docs/reference/kubernetes-api/_index.md
@@ -1,6 +1,10 @@
---
title: "Kubernetes API"
weight: 50
+card:
+ title: Kubernetes API reference
+ name: reference
+ weight: 40
---
diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index b2c0ec9aec..797fc601b9 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -3,6 +3,12 @@ title: Well-Known Labels, Annotations and Taints
content_type: concept
weight: 40
no_list: true
+card:
+ name: reference
+ weight: 30
+ anchors:
+ - anchor: "#labels-annotations-and-taints-used-on-api-objects"
+ title: Labels, annotations and taints
---
diff --git a/content/en/docs/reference/setup-tools/kubeadm/_index.md b/content/en/docs/reference/setup-tools/kubeadm/_index.md
index 00120e3d9d..f19559f7c6 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/_index.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/_index.md
@@ -4,8 +4,9 @@ weight: 10
no_list: true
content_type: concept
card:
- name: reference
- weight: 40
+ title: kubeadm command reference
+ name: setup
+ weight: 80
---
Kubeadm is a tool built to provide `kubeadm init` and `kubeadm join` as best-practice "fast paths" for creating Kubernetes clusters.
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 50f7f6557e..98c004e38d 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
@@ -4,7 +4,7 @@ content_type: task
weight: 10
card:
name: setup
- weight: 20
+ weight: 40
title: Install the kubeadm setup tool
---
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 2340278514..cca5d49d6e 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
@@ -4,7 +4,8 @@ content_type: task
weight: 30
card:
name: tasks
- weight: 40
+ weight: 25
+ title: Configure access to clusters
---
diff --git a/content/en/docs/tasks/debug/_index.md b/content/en/docs/tasks/debug/_index.md
index 1adde2a7c4..f5a643affe 100644
--- a/content/en/docs/tasks/debug/_index.md
+++ b/content/en/docs/tasks/debug/_index.md
@@ -7,6 +7,10 @@ reviewers:
- davidopp
content_type: concept
no_list: true
+card:
+ name: tasks
+ weight: 999
+ title: Getting help
---
diff --git a/content/en/docs/tasks/tools/_index.md b/content/en/docs/tasks/tools/_index.md
index f928931c01..679b7a1e35 100644
--- a/content/en/docs/tasks/tools/_index.md
+++ b/content/en/docs/tasks/tools/_index.md
@@ -3,6 +3,12 @@ title: "Install Tools"
description: Set up Kubernetes tools on your computer.
weight: 10
no_list: true
+card:
+ name: tasks
+ weight: 20
+ anchors:
+ - anchor: "#kubectl"
+ title: Install kubectl
---
## kubectl
diff --git a/content/en/docs/tasks/tools/install-kubectl-linux.md b/content/en/docs/tasks/tools/install-kubectl-linux.md
index 4c2e1deebf..d6eeee14e5 100644
--- a/content/en/docs/tasks/tools/install-kubectl-linux.md
+++ b/content/en/docs/tasks/tools/install-kubectl-linux.md
@@ -4,10 +4,6 @@ reviewers:
title: Install and Set Up kubectl on Linux
content_type: task
weight: 10
-card:
- name: tasks
- weight: 20
- title: Install kubectl on Linux
---
## {{% heading "prerequisites" %}}
diff --git a/content/en/docs/tasks/tools/install-kubectl-macos.md b/content/en/docs/tasks/tools/install-kubectl-macos.md
index aa1071bbd1..4e37bbbb29 100644
--- a/content/en/docs/tasks/tools/install-kubectl-macos.md
+++ b/content/en/docs/tasks/tools/install-kubectl-macos.md
@@ -4,10 +4,6 @@ reviewers:
title: Install and Set Up kubectl on macOS
content_type: task
weight: 10
-card:
- name: tasks
- weight: 20
- title: Install kubectl on macOS
---
## {{% heading "prerequisites" %}}
diff --git a/content/en/docs/tasks/tools/install-kubectl-windows.md b/content/en/docs/tasks/tools/install-kubectl-windows.md
index 8a1c65fcad..ca18ff7026 100644
--- a/content/en/docs/tasks/tools/install-kubectl-windows.md
+++ b/content/en/docs/tasks/tools/install-kubectl-windows.md
@@ -4,10 +4,6 @@ reviewers:
title: Install and Set Up kubectl on Windows
content_type: task
weight: 10
-card:
- name: tasks
- weight: 20
- title: Install kubectl on Windows
---
## {{% heading "prerequisites" %}}
From d2ae666ee9470ad0fa409a0c964a61ff916c87be Mon Sep 17 00:00:00 2001
From: Michael
Date: Wed, 9 Aug 2023 20:46:52 +0800
Subject: [PATCH 218/446] [zh] Fix issues in install-kubectl-windows.md
(#42470)
---
content/zh-cn/docs/tasks/tools/install-kubectl-windows.md | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md b/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md
index 6bdfa8c25a..f6046b9d1c 100644
--- a/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md
+++ b/content/zh-cn/docs/tasks/tools/install-kubectl-windows.md
@@ -54,14 +54,10 @@ The following methods exist for installing kubectl on Windows:
-->
### 用 curl 在 Windows 上安装 kubectl {#install-kubectl-binary-with-curl-on-windows}
-
-
1. 下载最新补丁版 {{< skew currentVersion >}}:
[kubectl {{< skew currentPatchVersion >}}](https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe)。
@@ -103,6 +99,7 @@ The following methods exist for installing kubectl on Windows:
+
- 在命令行环境中,手工对比 `CertUtil` 命令的输出与校验和文件:
```cmd
@@ -114,6 +111,7 @@ The following methods exist for installing kubectl on Windows:
- Using PowerShell to automate the verification using the `-eq` operator to
get a `True` or `False` result:
-->
+
- 用 PowerShell 自动验证,用运算符 `-eq` 来直接取得 `True` 或 `False` 的结果:
```powershell
@@ -125,7 +123,6 @@ The following methods exist for installing kubectl on Windows:
1. Test to ensure the version of `kubectl` is the same as downloaded:
-->
-
3. 将 `kubectl` 二进制文件夹追加或插入到你的 `PATH` 环境变量中。
4. 测试一下,确保此 `kubectl` 的版本和期望版本一致:
@@ -323,6 +320,7 @@ kubectl 为 Bash、Zsh、Fish 和 PowerShell 提供自动补全功能,可以
+
- 用提示的命令对 `CertUtil` 的输出和下载的校验和文件进行手动比较。
```cmd
From 35420c581c5b851173cb3014e0ada0cecffa3051 Mon Sep 17 00:00:00 2001
From: xin gu <418294249@qq.com>
Date: Wed, 9 Aug 2023 22:32:39 +0800
Subject: [PATCH 219/446] sync quality-service-pod resize-container-resources
update-api-object-kubectl-patch
---
.../tasks/configure-pod-container/quality-service-pod.md | 8 ++++----
.../configure-pod-container/resize-container-resources.md | 2 +-
.../update-api-object-kubectl-patch.md | 6 +++---
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/zh-cn/docs/tasks/configure-pod-container/quality-service-pod.md b/content/zh-cn/docs/tasks/configure-pod-container/quality-service-pod.md
index ea542e246b..2565e81620 100644
--- a/content/zh-cn/docs/tasks/configure-pod-container/quality-service-pod.md
+++ b/content/zh-cn/docs/tasks/configure-pod-container/quality-service-pod.md
@@ -95,7 +95,7 @@ memory request, both equal to 200 MiB. The Container has a CPU limit and a CPU r
下面是包含一个 Container 的 Pod 清单。该 Container 设置了内存请求和内存限制,值都是 200 MiB。
该 Container 设置了 CPU 请求和 CPU 限制,值都是 700 milliCPU:
-{{< codenew file="pods/qos/qos-pod.yaml" >}}
+{{% code file="pods/qos/qos-pod.yaml" %}}
## 使用带 retainKeys 策略的策略合并 patch 更新 Deployment {#use-strategic-merge-patch-to-update-a-deployment-using-the-retainkeys-strategy}
-{{% codenew file="application/deployment-retainkeys.yaml" %}}
+{{% code file="application/deployment-retainkeys.yaml" %}}
下面是一个定义了 `podFailurePolicy` 的 Job 的清单:
-{{< codenew file="/controllers/job-pod-failure-policy-example.yaml" >}}
+{{% code file="/controllers/job-pod-failure-policy-example.yaml" %}}
-如果 Job 是在特性门控 `JobTrackingWithFinalizers` 被禁用时创建的,即使你将控制面升级到 1.26,
-控制面也不会使用 Finalizer 跟踪 Job。
-{{< /note >}}
-
控制面会跟踪属于任何 Job 的 Pod,并通知是否有任何这样的 Pod 被从 API 服务器中移除。
为了实现这一点,Job 控制器创建的 Pod 带有 Finalizer `batch.kubernetes.io/job-tracking`。
控制器只有在 Pod 被记入 Job 状态后才会移除 Finalizer,允许 Pod 可以被其他控制器或用户移除。
-在升级到 Kubernetes 1.26 之前或在启用特性门控 `JobTrackingWithFinalizers`
-之前创建的 Job 被跟踪时不使用 Pod Finalizer。
-Job {{< glossary_tooltip term_id="controller" text="控制器" >}}仅根据集群中存在的 Pod
-更新 `succeeded` 和 `failed` Pod 的状态计数器。如果 Pod 被从集群中删除,控制面可能无法跟踪 Job 的进度。
-
-
-你可以根据检查 Job 是否含有 `batch.kubernetes.io/job-tracking` 注解,
-来确定控制面是否正在使用 Pod Finalizer 追踪 Job。
-你**不**应该给 Job 手动添加或删除该注解。
-取而代之的是你可以重新创建 Job 以确保使用 Pod Finalizer 跟踪这些 Job。
-
diff --git a/content/zh-cn/docs/concepts/workloads/controllers/replicaset.md b/content/zh-cn/docs/concepts/workloads/controllers/replicaset.md
index fbe20e17b5..78ce34407c 100644
--- a/content/zh-cn/docs/concepts/workloads/controllers/replicaset.md
+++ b/content/zh-cn/docs/concepts/workloads/controllers/replicaset.md
@@ -113,7 +113,7 @@ Deployment,并在 spec 部分定义你的应用。
-->
## 示例 {#example}
-{{< codenew file="controllers/frontend.yaml" >}}
+{{% code file="controllers/frontend.yaml" %}}
@@ -34,7 +40,7 @@ always up and available.
### addonmanager.kubernetes.io/mode
@@ -785,7 +785,7 @@ For more details, see [Addon-manager](https://github.com/kubernetes/kubernetes/b
- `Ignore`:插件资源将被忽略。此模式对于与外接插件管理器不兼容或由其他控制器管理的插件程序非常有用。
有关详细信息,请参见
-[Addon-manager](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/addon-manager/README.md)
+[Addon-manager](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/addon-manager/README.md)。
Kubernetes 对 Zone 和 Region 的结构做了一些假设:
@@ -1540,7 +1540,7 @@ Example: `volume.beta.kubernetes.io/storage-provisioner: "k8s.io/minikube-hostpa
Used on: PersistentVolumeClaim
This annotation has been deprecated since v1.23.
-See [volume.kubernetes.io/storage-provisioner](#volume-kubernetes-io-storage-provisioner)
+See [volume.kubernetes.io/storage-provisioner](#volume-kubernetes-io-storage-provisioner).
-->
### volume.beta.kubernetes.io/storage-provisioner (已弃用) {#volume-beta-kubernetes-io-storage-provisioner}
@@ -1581,7 +1581,7 @@ This annotation has been deprecated. Instead, set the
[`storageClassName` field](/docs/concepts/storage/persistent-volumes/#class)
for the PersistentVolumeClaim or PersistentVolume.
-->
-此注解可以为 PersistentVolume (PV) 或 PersistentVolumeClaim (PVC) 指定
+此注解可以为 PersistentVolume(PV)或 PersistentVolumeClaim(PVC)指定
[StorageClass](/zh-cn/docs/concepts/storage/storage-classes/)。
当 `storageClassName` 属性和 `volume.beta.kubernetes.io/storage-class` 注解均被指定时,
注解 `volume.beta.kubernetes.io/storage-class` 将优先于 `storageClassName` 属性。
@@ -1997,7 +1997,7 @@ resource without a class specified will be assigned this default class.
资源将被设置为此默认类。
-### alpha.kubernetes.io/provided-node-ip {#alpha-kubernetes-io-provided-node-ip}
+### alpha.kubernetes.io/provided-node-ip (alpha) {#alpha-kubernetes-io-provided-node-ip}
类别:注解
@@ -2094,8 +2094,7 @@ container.
此注解已被弃用。取而代之的是使用
[`kubectl.kubernetes.io/default-container`](#kubectl-kubernetes-io-default-container) 注解。
@@ -2143,11 +2142,8 @@ Example: `batch.kubernetes.io/job-tracking: ""`
Used on: Jobs
-The presence of this annotation on a Job indicates that the control plane is
+The presence of this annotation on a Job used to indicate that the control plane is
[tracking the Job status using finalizers](/docs/concepts/workloads/controllers/job/#job-tracking-with-finalizers).
-The control plane uses this annotation to safely transition to tracking Jobs
-using finalizers, while the feature is in development.
-You should **not** manually add or remove this annotation.
-->
### batch.kubernetes.io/job-tracking (已弃用) {#batch-kubernetes-io-job-tracking}
@@ -2158,18 +2154,13 @@ You should **not** manually add or remove this annotation.
用于:Job
Job 上存在此注解表明控制平面正在[使用 Finalizer 追踪 Job](/zh-cn/docs/concepts/workloads/controllers/job/#job-tracking-with-finalizers)。
-控制平面使用此注解来安全地转换为使用 Finalizer 追踪 Job,而此特性正在开发中。
-你 **不** 可以手动添加或删除此注解。
-{{< note >}}
-从 Kubernetes 1.26 开始,该注解被弃用。
-Kubernetes 1.27 及以上版本将忽略此注解,并始终使用 Finalizer 追踪 Job。
-{{< /note >}}
+添加或删除此注解不再有效(Kubernetes v1.27 及更高版本),
+所有 Job 均通过 Finalizer 进行追踪。
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.)
+In Kubernetes {{< skew currentVersion >}} there are two versions of KMS at-rest encryption.
+You should use KMS v2 if feasible because KMS v1 is deprecated (since Kubernetes v1.28).
+However, you should also read and observe the **Caution** notices in this page that highlight specific
+cases when you must not use KMS v2. KMS v2 offers significantly better performance characteristics than KMS v1.
## {{% 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. Kubernetes recommends using KMS v2.
-- 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 >}}
(if you are running a different version of Kubernetes that also supports the v2 KMS
API, switch to the documentation for that version of Kubernetes).
+- If you selected KMS API v1 to support clusters prior to version v1.27
+ or if you have a legacy KMS plugin that only supports KMS v1,
+ any supported Kubernetes version will work. This API is deprecated as of Kubernetes v1.28.
+ Kubernetes does not recommend the use of this API.
{{< version-check >}}
### KMS v1
-{{< feature-state for_k8s_version="v1.12" state="beta" >}}
+{{< feature-state for_k8s_version="v1.28" state="deprecated" >}}
* Kubernetes version 1.10.0 or later is required
@@ -38,13 +42,22 @@ you have selected.
* 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.
-
+ For environments where all API servers are running version 1.28 or later, and you do not require the ability
+ to downgrade to Kubernetes v1.27, you can enable the `KMSv2KDF` feature gate (a beta feature) for more
+ robust data encryption key generation. The Kubernetes project recommends enabling KMS v2 KDF if those
+ preconditions are met.
+
* Your cluster must use etcd v3 or later
{{< 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.
+
+---
+
+Running mixed API server versions with some servers at v1.27, and others at v1.28 _with the
+`KMSv2KDF` feature gate enabled_ is **not supported** - and is likely to result in data loss.
{{< /caution >}}
@@ -52,18 +65,33 @@ enabled will result in data loss.
The KMS encryption provider uses an envelope encryption scheme to encrypt data in etcd.
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.
+
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).
+
+With KMS v2, there are two ways for the API server to generate a DEK.
+Kubernetes defaults to generating a new DEK at API server startup, which is then reused
+for resource encryption. However, if you use KMS v2 _and_ enable the `KMSv2KDF`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/), then
+Kubernetes instead generates a new DEK **per encryption**: the API server uses a
+_key derivation function_ to generate single use data encryption keys from a secret seed
+combined with some random data.
+Whichever approach you configure, the DEK or seed is also rotated whenever the KEK is rotated
+(see `Understanding key_id and Key Rotation` section below for more details).
+
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.
+
+If you are running virtual machine (VM) based nodes that leverage VM state store with this feature,
+using KMS v2 is **insecure** and an information security risk unless you also explicitly enable
+the `KMSv2KDF`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
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.
@@ -72,6 +100,13 @@ 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.
+
+If you have enabled the `KMSv2KDF`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) _and_ are using KMS v2
+(not KMS v1), the API server generates single use data encryption keys from a secret seed.
+This eliminates the need for a counter based nonce while avoiding nonce collision concerns.
+It also removes any specific concerns with using KMS v2 and VM state store.
+
{{< /caution >}}
## Configuring the KMS provider
@@ -108,7 +143,7 @@ See [Understanding the encryption at rest configuration](/docs/tasks/administer-
To implement a KMS plugin, you can develop a new plugin gRPC server or enable a KMS plugin
already provided by your cloud provider.
-You then integrate the plugin with the remote KMS and deploy it on the Kubernetes master.
+You then integrate the plugin with the remote KMS and deploy it on the Kubernetes control plane.
### Enabling the KMS supported by your cloud provider
@@ -222,8 +257,9 @@ Then use the functions and data structures in the stub file to develop the serve
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 >}}
+ Because you don't control the number of writes performed with the DEK,
+ the Kubernetes project recommends rotating the KEK at least every 90 days.
{{< /caution >}}
* protocol: UNIX domain socket (`unix`)
@@ -248,7 +284,7 @@ for decryption (KMS v2 makes this process easier by providing a dedicated `annot
### Deploying the KMS plugin
-Ensure that the KMS plugin runs on the same host(s) as the Kubernetes master(s).
+Ensure that the KMS plugin runs on the same host(s) as the Kubernetes API server(s).
## Encrypting your data with the KMS provider
From ca8ad1b3f5d408f33be36b70caadccd92a775215 Mon Sep 17 00:00:00 2001
From: Jeremy Rickard
Date: Wed, 9 Aug 2023 08:23:51 -0600
Subject: [PATCH 223/446] delay august patch releases
Signed-off-by: Jeremy Rickard
---
content/en/releases/patch-releases.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/releases/patch-releases.md b/content/en/releases/patch-releases.md
index b1cd4013b6..ea9e712552 100644
--- a/content/en/releases/patch-releases.md
+++ b/content/en/releases/patch-releases.md
@@ -78,7 +78,7 @@ releases may also occur in between these.
| Monthly Patch Release | Cherry Pick Deadline | Target date |
| --------------------- | -------------------- | ----------- |
-| August 2023 | 2023-08-04 | 2023-08-09 |
+| August 2023 | 2023-08-04 | 2023-08-23 |
| September 2023 | 2023-09-08 | 2023-09-13 |
| October 2023 | 2023-10-13 | 2023-10-18 |
| November 2023 | N/A | N/A |
From 76c22d077563bef2f6f93cca75f278680049e9f3 Mon Sep 17 00:00:00 2001
From: Jeremy Rickard
Date: Wed, 9 Aug 2023 14:21:40 -0600
Subject: [PATCH 224/446] Add update to schedule.yaml
Signed-off-by: Jeremy Rickard
---
data/releases/schedule.yaml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/data/releases/schedule.yaml b/data/releases/schedule.yaml
index 3c4f1c3d2a..803217607a 100644
--- a/data/releases/schedule.yaml
+++ b/data/releases/schedule.yaml
@@ -9,7 +9,7 @@ schedules:
next:
release: 1.27.5
cherryPickDeadline: 2023-08-04
- targetDate: 2023-08-09
+ targetDate: 2023-08-23
previousPatches:
- release: 1.27.4
cherryPickDeadline: 2023-07-14
@@ -35,7 +35,7 @@ schedules:
next:
release: 1.26.8
cherryPickDeadline: 2023-08-04
- targetDate: 2023-08-09
+ targetDate: 2023-08-23
previousPatches:
- release: 1.26.7
cherryPickDeadline: 2023-07-14
@@ -70,7 +70,7 @@ schedules:
next:
release: 1.25.13
cherryPickDeadline: 2023-08-04
- targetDate: 2023-08-09
+ targetDate: 2023-08-23
previousPatches:
- release: 1.25.12
cherryPickDeadline: 2023-07-14
From ef010e77e450e6c5f21ef96d7c6923109aaacc03 Mon Sep 17 00:00:00 2001
From: Kevin Hannon
Date: Wed, 9 Aug 2023 16:23:31 -0400
Subject: [PATCH 225/446] fix a typo for podReplacementPolicy
---
content/en/docs/concepts/workloads/controllers/job.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 20d9b33653..4a9f4b65a1 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -538,7 +538,7 @@ ensures that deleted pods have their finalizers removed by the Job controller.
{{< note >}}
Starting with Kubernetes v1.28, when Pod failure policy is used, the Job controller recreates
terminating Pods only once these Pods reach the terminal `Failed` phase. This behavior is similar
-to `podRecreationPolicy: Failed`. For more information, see [Pod replacement policy](#pod-replacement-policy).
+to `podReplacementPolicy: Failed`. For more information, see [Pod replacement policy](#pod-replacement-policy).
{{< /note >}}
## Job termination and cleanup
@@ -946,7 +946,7 @@ You may choose to create replacement Pods only when the terminating Pod is fully
This will only recreate Pods once they are terminated.
The default replacement policy depends on whether the Job has a `podFailurePolicy` set.
With no Pod failure policy defined for a Job, omitting the `podReplacementPolicy` field selects the
-`FailedOrTerminating` replacement policy:
+`TerminatingOrFailed` replacement policy:
the control plane creates replacement Pods immediately upon Pod deletion
(as soon as the control plane sees that a Pod for this Job has `deletionTimestamp` set).
For Jobs with a Pod failure policy set, the default `podReplacementPolicy` is `Failed`, and no other
From 37a8a5a1f425b902c12102f5864b605ca69e66b0 Mon Sep 17 00:00:00 2001
From: windsonsea
Date: Thu, 10 Aug 2023 09:44:53 +0800
Subject: [PATCH 226/446] Clean up distribute-credentials-secure.md
---
.../distribute-credentials-secure.md | 149 ++++++++++--------
1 file changed, 83 insertions(+), 66 deletions(-)
diff --git a/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md b/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
index e5d80ad72a..144352fbb0 100644
--- a/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
+++ b/content/en/docs/tasks/inject-data-application/distribute-credentials-secure.md
@@ -112,12 +112,14 @@ Here is a configuration file you can use to create a Pod:
```
Output:
+
```
NAME READY STATUS RESTARTS AGE
secret-test-pod 1/1 Running 0 42m
```
1. Get a shell into the Container that is running in your Pod:
+
```shell
kubectl exec -i -t secret-test-pod -- /bin/bash
```
@@ -126,22 +128,28 @@ Here is a configuration file you can use to create a Pod:
`/etc/secret-volume`.
In your shell, list the files in the `/etc/secret-volume` directory:
+
```shell
# Run this in the shell inside the container
ls /etc/secret-volume
```
+
The output shows two files, one for each piece of secret data:
+
```
password username
```
1. In your shell, display the contents of the `username` and `password` files:
+
```shell
# Run this in the shell inside the container
echo "$( cat /etc/secret-volume/username )"
echo "$( cat /etc/secret-volume/password )"
```
+
The output is your username and password:
+
```
my-app
39528$vdg7Jb
@@ -153,8 +161,8 @@ in this directory.
### Project Secret keys to specific file paths
-You can also control the paths within the volume where Secret keys are projected. Use the `.spec.volumes[].secret.items` field to change the target
-path of each key:
+You can also control the paths within the volume where Secret keys are projected. Use the
+`.spec.volumes[].secret.items` field to change the target path of each key:
```yaml
apiVersion: v1
@@ -260,13 +268,14 @@ secrets change.
kubectl create -f https://k8s.io/examples/pods/inject/pod-single-secret-env-variable.yaml
```
-- In your shell, display the content of `SECRET_USERNAME` container environment variable
+- In your shell, display the content of `SECRET_USERNAME` container environment variable.
```shell
kubectl exec -i -t env-single-secret -- /bin/sh -c 'echo $SECRET_USERNAME'
```
- The output is
+ The output is similar to:
+
```
backend-admin
```
@@ -290,12 +299,14 @@ secrets change.
kubectl create -f https://k8s.io/examples/pods/inject/pod-multiple-secret-env-variable.yaml
```
-- In your shell, display the container environment variables
+- In your shell, display the container environment variables.
```shell
kubectl exec -i -t envvars-multiple-secrets -- /bin/sh -c 'env | grep _USERNAME'
```
- The output is
+
+ The output is similar to:
+
```
DB_USERNAME=db-admin
BACKEND_USERNAME=backend-admin
@@ -313,7 +324,8 @@ This functionality is available in Kubernetes v1.6 and later.
kubectl create secret generic test-secret --from-literal=username='my-app' --from-literal=password='39528$vdg7Jb'
```
-- Use envFrom to define all of the Secret's data as container environment variables. The key from the Secret becomes the environment variable name in the Pod.
+- Use envFrom to define all of the Secret's data as container environment variables.
+ The key from the Secret becomes the environment variable name in the Pod.
{{% code file="pods/inject/pod-secret-envFrom.yaml" %}}
@@ -323,13 +335,14 @@ This functionality is available in Kubernetes v1.6 and later.
kubectl create -f https://k8s.io/examples/pods/inject/pod-secret-envFrom.yaml
```
-- In your shell, display `username` and `password` container environment variables
+- In your shell, display `username` and `password` container environment variables.
```shell
kubectl exec -i -t envfrom-secret -- /bin/sh -c 'echo "username: $username\npassword: $password\n"'
```
- The output is
+ The output is similar to:
+
```
username: my-app
password: 39528$vdg7Jb
@@ -364,72 +377,76 @@ another Pod which consumes a secret with test environment credentials.
secret "test-db-secret" created
```
- {{< note >}}
- Special characters such as `$`, `\`, `*`, `=`, and `!` will be interpreted by your
- [shell](https://en.wikipedia.org/wiki/Shell_(computing)) and require escaping.
+ {{< note >}}
+ Special characters such as `$`, `\`, `*`, `=`, and `!` will be interpreted by your
+ [shell](https://en.wikipedia.org/wiki/Shell_(computing)) and require escaping.
- In most shells, the easiest way to escape the password is to surround it with single quotes (`'`).
- For example, if your actual password is `S!B\*d$zDsb=`, you should execute the command as follows:
+ In most shells, the easiest way to escape the password is to surround it with single quotes (`'`).
+ For example, if your actual password is `S!B\*d$zDsb=`, you should execute the command as follows:
- ```shell
- kubectl create secret generic dev-db-secret --from-literal=username=devuser --from-literal=password='S!B\*d$zDsb='
- ```
+ ```shell
+ kubectl create secret generic dev-db-secret --from-literal=username=devuser --from-literal=password='S!B\*d$zDsb='
+ ```
- You do not need to escape special characters in passwords from files (`--from-file`).
- {{< /note >}}
+ You do not need to escape special characters in passwords from files (`--from-file`).
+ {{< /note >}}
1. Create the Pod manifests:
- ```shell
- cat < pod.yaml
- apiVersion: v1
- kind: List
- items:
- - kind: Pod
- apiVersion: v1
- metadata:
- name: prod-db-client-pod
- labels:
- name: prod-db-client
- spec:
- volumes:
- - name: secret-volume
- secret:
- secretName: prod-db-secret
- containers:
- - name: db-client-container
- image: myClientImage
- volumeMounts:
- - name: secret-volume
- readOnly: true
- mountPath: "/etc/secret-volume"
- - kind: Pod
- apiVersion: v1
- metadata:
- name: test-db-client-pod
- labels:
- name: test-db-client
- spec:
- volumes:
- - name: secret-volume
- secret:
- secretName: test-db-secret
- containers:
- - name: db-client-container
- image: myClientImage
- volumeMounts:
- - name: secret-volume
- readOnly: true
- mountPath: "/etc/secret-volume"
- EOF
- ```
- Note how the specs for the two Pods differ only in one field; this facilitates creating Pods with different capabilities from a common Pod template.
+ ```shell
+ cat < pod.yaml
+ apiVersion: v1
+ kind: List
+ items:
+ - kind: Pod
+ apiVersion: v1
+ metadata:
+ name: prod-db-client-pod
+ labels:
+ name: prod-db-client
+ spec:
+ volumes:
+ - name: secret-volume
+ secret:
+ secretName: prod-db-secret
+ containers:
+ - name: db-client-container
+ image: myClientImage
+ volumeMounts:
+ - name: secret-volume
+ readOnly: true
+ mountPath: "/etc/secret-volume"
+ - kind: Pod
+ apiVersion: v1
+ metadata:
+ name: test-db-client-pod
+ labels:
+ name: test-db-client
+ spec:
+ volumes:
+ - name: secret-volume
+ secret:
+ secretName: test-db-secret
+ containers:
+ - name: db-client-container
+ image: myClientImage
+ volumeMounts:
+ - name: secret-volume
+ readOnly: true
+ mountPath: "/etc/secret-volume"
+ EOF
+ ```
+
+ {{< note >}}
+ How the specs for the two Pods differ only in one field; this facilitates creating Pods
+ with different capabilities from a common Pod template.
+ {{< /note >}}
1. Apply all those objects on the API server by running:
- ```shell
- kubectl create -f pod.yaml
- ```
+ ```shell
+ kubectl create -f pod.yaml
+ ```
Both containers will have the following files present on their filesystems with the values
for each container's environment:
From 44ced6f09a55b4f872c4963beb04544c4f52213d Mon Sep 17 00:00:00 2001
From: Sreeram Venkitesh
Date: Thu, 10 Aug 2023 10:23:38 +0530
Subject: [PATCH 227/446] Added new contributor ambassador role to contributing
guide
---
content/en/docs/contribute/_index.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content/en/docs/contribute/_index.md b/content/en/docs/contribute/_index.md
index b4c7d838fa..beb6446404 100644
--- a/content/en/docs/contribute/_index.md
+++ b/content/en/docs/contribute/_index.md
@@ -158,6 +158,10 @@ Figure 2. Preparation for your first contribution.
- Learn about [page content types](/docs/contribute/style/page-content-types/)
and [Hugo shortcodes](/docs/contribute/style/hugo-shortcodes/).
+## Getting help when contributing
+
+Making your first contribution can be overwhelming. The [New Contributor Ambassadors](https://github.com/kubernetes/website#new-contributor-ambassadors) are there to walk you through making your first few contributions. You can reach out to them in the [Kubernetes Slack](https://slack.k8s.io/) preferably in the `#sig-docs` channel. There is also the [New Contributors Meet and Greet call](https://www.kubernetes.dev/resources/calendar/) that happens on the first Tuesday of every month. You can interact with the New Contributor Ambassadors and get your queries resolved here.
+
## Next steps
- Learn to [work from a local clone](/docs/contribute/new-content/open-a-pr/#fork-the-repo)
From ec6bda421eb1670fb1966fffac1e2304a9494fb5 Mon Sep 17 00:00:00 2001
From: Michal Wozniak
Date: Thu, 10 Aug 2023 11:19:26 +0200
Subject: [PATCH 228/446] Fix the link to pod replacement policy
---
content/en/docs/concepts/workloads/controllers/job.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index 4a9f4b65a1..2152cf4144 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -931,7 +931,7 @@ 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.
-### Delayed creation of replacement pods
+### Delayed creation of replacement pods {#pod-replacement-policy}
{{< feature-state for_k8s_version="v1.28" state="alpha" >}}
From c206802a2e8f40fdc26e97972137c23eb6b8a3f5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marko=20Mudrini=C4=87?=
Date: Fri, 4 Aug 2023 19:34:25 +0200
Subject: [PATCH 229/446] Update package manager instructions with
community-hosted repos
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Marko Mudrinić