Container Config to run nginx (must be embedded in a PodSpec to run).
@@ -94,8 +94,6 @@ container.
name:nginx# Run the nginx:1.10 imageimage:nginx:1.10
-
-
Container Config to run nginx (must be embedded in a PodSpec to run).
@@ -104,8 +102,6 @@ container.
name:nginx# Run the nginx:1.10 imageimage:nginx:1.10
-
-
@@ -117,9 +113,9 @@ container.
-
Core
-
v1
-
Container
+
core
+
v1
+
Container
@@ -146,87 +142,87 @@ Appears In:
-
args string array
+
args string array
Arguments to the entrypoint. The docker image's CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell
-
command string array
+
command string array
Entrypoint array. Not executed within a shell. The docker image's ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container's environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell
-
env EnvVar array patch type: merge patch merge key: name
+
env EnvVar array patch type: merge patch merge key: name
List of environment variables to set in the container. Cannot be updated.
List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.
-
image string
+
image string
Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.
List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0.0.0" address inside a container will be accessible from the network. Cannot be updated.
Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.
-
stdinOnce boolean
+
stdinOnce boolean
Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false
-
terminationMessagePath string
+
terminationMessagePath string
Optional: Path at which the file to which the container's termination message will be written is mounted into the container's filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.
-
terminationMessagePolicy string
+
terminationMessagePolicy string
Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.
-
tty boolean
+
tty boolean
Whether this container should allocate a TTY for itself, also requires 'stdin' to be true. Default is false.
Pod volumes to mount into the container's filesystem. Cannot be updated.
-
workingDir string
+
workingDir string
Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated.
@@ -248,41 +244,41 @@ Appears In:
-
containerID string
+
containerID string
Container's ID in the format 'docker://<container_id>'.
Details about the container's last termination condition.
-
name string
+
name string
This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.
-
ready boolean
+
ready boolean
Specifies whether the container has passed its readiness probe.
-
restartCount integer
+
restartCount integer
The number of times the container has been restarted, currently based on the number of dead containers that have not yet been removed. Note that this is calculated from dead containers. But those containers are subject to garbage collection. This value will get capped at 5 by GC.
Specifies how to treat concurrent executions of a Job. Valid values are: - "Allow" (default): allows CronJobs to run concurrently; - "Forbid": forbids concurrent runs, skipping next run if previous run hasn't finished yet; - "Replace": cancels currently running job and replaces it with a new one
-
failedJobsHistoryLimit integer
+
failedJobsHistoryLimit integer
The number of failed finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a CronJob
HTTP Request
@@ -779,11 +759,11 @@ Appears In:
-
name
+
name
name of the CronJob
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -798,19 +778,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of CronJob
HTTP Request
@@ -887,7 +863,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -902,39 +878,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -962,28 +938,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified CronJob
HTTP Request
@@ -998,11 +970,11 @@ Appears In:
-
name
+
name
name of the CronJob
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -1017,15 +989,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -1051,28 +1023,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind CronJob
HTTP Request
@@ -1087,7 +1055,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -1102,39 +1070,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -1160,28 +1128,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind CronJob
HTTP Request
@@ -1196,39 +1160,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -1254,28 +1218,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind CronJob
HTTP Request
@@ -1290,11 +1250,11 @@ Appears In:
-
name
+
name
name of the CronJob
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -1309,39 +1269,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -1367,28 +1327,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of CronJob
HTTP Request
@@ -1403,7 +1359,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -1418,39 +1374,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -1476,28 +1432,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of CronJob
HTTP Request
@@ -1512,39 +1464,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -1572,28 +1524,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified CronJob
HTTP Request
@@ -1608,11 +1556,11 @@ Appears In:
-
name
+
name
name of the CronJob
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).
-
revisionHistoryLimit integer
+
revisionHistoryLimit integer
The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.
An update strategy to replace existing DaemonSet pods with new pods.
@@ -2019,43 +1957,43 @@ Appears In:
-
collisionCount integer
+
collisionCount integer
Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
-
conditions DaemonSetCondition array patch type: merge patch merge key: type
+
conditions DaemonSetCondition array patch type: merge patch merge key: type
Represents the latest available observations of a DaemonSet's current state.
The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)
The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.
-
numberUnavailable integer
+
numberUnavailable integer
The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)
-
observedGeneration integer
+
observedGeneration integer
The most recent generation observed by the daemon set controller.
-
updatedNumberScheduled integer
+
updatedNumberScheduled integer
The total number of nodes that are running updated daemon pod
The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.
object name and auth scope, such as for teams and projects
@@ -2582,19 +2503,19 @@ orphanDependents: false
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of DaemonSet
HTTP Request
@@ -2671,7 +2588,7 @@ orphanDependents: false
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -2686,39 +2603,39 @@ orphanDependents: false
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -2746,29 +2663,23 @@ orphanDependents: false
$ kubectl get daemonset daemonset-example -o json
-
curl Command (requires kubectl proxy to be running)
-$ kubectl proxy
-$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example
-
+$ kubectl proxy
+$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example
Output
-
-
Response Body
-
-
read the specified DaemonSet
HTTP Request
@@ -2783,11 +2694,11 @@ $ kubectl get daemonset daemonset-
-
name
+
name
name of the DaemonSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -2802,15 +2713,15 @@ $ kubectl get daemonset daemonset-
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -2836,28 +2747,24 @@ $ kubectl get daemonset daemonset-
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind DaemonSet
HTTP Request
@@ -2872,7 +2779,7 @@ $ kubectl get daemonset daemonset-
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -2887,39 +2794,39 @@ $ kubectl get daemonset daemonset-
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -2945,28 +2852,24 @@ $ kubectl get daemonset daemonset-
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind DaemonSet
HTTP Request
@@ -2981,39 +2884,39 @@ $ kubectl get daemonset daemonset-
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -3039,28 +2942,24 @@ $ kubectl get daemonset daemonset-
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind DaemonSet
HTTP Request
@@ -3075,11 +2974,11 @@ $ kubectl get daemonset daemonset-
-
name
+
name
name of the DaemonSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -3094,39 +2993,39 @@ $ kubectl get daemonset daemonset-
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -3152,28 +3051,24 @@ $ kubectl get daemonset daemonset-
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of DaemonSet
HTTP Request
@@ -3188,7 +3083,7 @@ $ kubectl get daemonset daemonset-
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -3203,39 +3098,39 @@ $ kubectl get daemonset daemonset-
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -3261,28 +3156,24 @@ $ kubectl get daemonset daemonset-
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of DaemonSet
HTTP Request
@@ -3297,39 +3188,39 @@ $ kubectl get daemonset daemonset-
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -3357,28 +3248,24 @@ $ kubectl get daemonset daemonset-
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified DaemonSet
HTTP Request
@@ -3393,11 +3280,11 @@ $ kubectl get daemonset daemonset-
-
name
+
name
name of the DaemonSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -3412,7 +3299,7 @@ $ kubectl get daemonset daemonset-
-
pretty
+
pretty
If 'true', then the output is pretty printed.
@@ -3427,7 +3314,7 @@ $ kubectl get daemonset daemonset-
Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)
-
paused boolean
+
paused boolean
Indicates that the deployment is paused.
-
progressDeadlineSeconds integer
+
progressDeadlineSeconds integer
The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.
-
replicas integer
+
replicas integer
Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.
-
revisionHistoryLimit integer
+
revisionHistoryLimit integer
The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.
Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment. It must match the pod template's labels.
Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.
-
collisionCount integer
+
collisionCount integer
Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.
-
conditions DeploymentCondition array patch type: merge patch merge key: type
+
conditions DeploymentCondition array patch type: merge patch merge key: type
Represents the latest available observations of a deployment's current state.
-
observedGeneration integer
+
observedGeneration integer
The generation observed by the deployment controller.
-
readyReplicas integer
+
readyReplicas integer
Total number of ready pods targeted by this deployment.
-
replicas integer
+
replicas integer
Total number of non-terminated pods targeted by this deployment (their labels match the selector).
-
unavailableReplicas integer
+
unavailableReplicas integer
Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.
-
updatedReplicas integer
+
updatedReplicas integer
Total number of non-terminated pods targeted by this deployment that have the desired template spec.
Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.
-
type string
+
type string
Type of deployment. Can be "Recreate" or "RollingUpdate". Default is RollingUpdate.
@@ -3909,12 +3784,12 @@ Appears In:
-
maxSurge
-
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.
+
maxSurge
+
The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.
-
maxUnavailable
-
The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old RC can be scaled down further, followed by scaling up the new RC, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.
+
maxUnavailable
+
The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.
object name and auth scope, such as for teams and projects
@@ -4562,19 +4418,19 @@ orphanDependents: false
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of Deployment
HTTP Request
@@ -4651,7 +4503,7 @@ orphanDependents: false
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -4666,39 +4518,39 @@ orphanDependents: false
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -4726,15 +4578,13 @@ orphanDependents: false
$ kubectl get deployment deployment-example -o json
-
curl Command (requires kubectl proxy to be running)
-$ kubectl proxy
-$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example
-
+$ kubectl proxy
+$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example
@@ -4901,11 +4747,11 @@ $ kubectl get deployment deployment-
-
name
+
name
name of the Deployment
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -4920,15 +4766,15 @@ $ kubectl get deployment deployment-
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -4954,7 +4800,6 @@ $ kubectl get deployment deployment-
$ kubectl get deployment -o json
-
curl Command (requires kubectl proxy to be running)
@@ -4962,7 +4807,6 @@ $ kubectl get deployment -o json
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments'
-
Output
@@ -5109,8 +4953,6 @@ $
kubectl proxy
}
]
}
-
-
Response Body
@@ -5257,8 +5099,6 @@ $
kubectl proxy
}
]
}
-
-
list or watch objects of kind Deployment
HTTP Request
@@ -5273,7 +5113,7 @@ $ kubectl proxy
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -5288,39 +5128,39 @@ $
kubectl proxy
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -5346,28 +5186,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Deployment
HTTP Request
@@ -5382,39 +5218,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -5440,7 +5276,6 @@ $ kubectl proxy
$ kubectl get deployment deployment-example --watch -o json
-
curl Command (requires kubectl proxy to be running)
@@ -5448,7 +5283,6 @@ $ kubectl get deployment deployment-example
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/watch/namespaces/default/deployments/deployment-example'
-
Output
@@ -5528,7 +5362,6 @@ $
kubectl proxy
}
}
}
-
Response Body
@@ -5608,7 +5441,6 @@ $
kubectl proxy
}
}
}
-
watch changes to an object of kind Deployment
HTTP Request
@@ -5623,11 +5455,11 @@ $ kubectl proxy
-
name
+
name
name of the Deployment
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -5642,39 +5474,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -5700,28 +5532,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Deployment
HTTP Request
@@ -5736,7 +5564,7 @@ $ kubectl proxy
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -5751,39 +5579,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -5809,28 +5637,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Deployment
HTTP Request
@@ -5845,39 +5669,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -5905,28 +5729,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified Deployment
HTTP Request
@@ -5941,11 +5761,11 @@ $ kubectl proxy
-
name
+
name
name of the Deployment
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
Job Config to print pi up to 2000 digits (then exit).
@@ -6478,8 +6278,6 @@ apiVersion: batch/v1
args: ["-Mbignum=bpi", "-wle", "print bpi(2000)"]
# Do not restart containers after they exit restartPolicy: Never
-
-
Job Config to print pi up to 2000 digits (then exit).
@@ -6502,8 +6300,6 @@ apiVersion: batch/v1
args: ["-Mbignum=bpi", "-wle", "print bpi(2000)"]
# Do not restart containers after they exit restartPolicy: Never
-
-
Specifies the duration in seconds relative to the startTime that the job may be active before the system tries to terminate it; value must be positive integer
-
backoffLimit integer
+
backoffLimit integer
Specifies the number of retries before marking this job failed. Defaults to 6
-
completions integer
+
completions integer
Specifies the desired number of successfully finished pods the job should be run with. Setting to nil means that the success of any pod signals the success of all pods, and allows parallelism to have any positive value. Setting to 1 means that parallelism is limited to 1 and the success of that pod signals the success of the job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
-
manualSelector boolean
+
manualSelector boolean
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
-
parallelism integer
+
parallelism integer
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/
Represents time when the job was completed. It is not guaranteed to be set in happens-before order across separate operations. It is represented in RFC3339 form and is in UTC.
-
conditions JobCondition array patch type: merge patch merge key: type
+
conditions JobCondition array patch type: merge patch merge key: type
Represents time when the job was acknowledged by the job controller. It is not guaranteed to be set in happens-before order across separate operations. It is represented in RFC3339 form and is in UTC.
object name and auth scope, such as for teams and projects
@@ -7128,19 +6907,19 @@ orphanDependents: false
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of Job
HTTP Request
@@ -7217,7 +6992,7 @@ orphanDependents: false
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -7232,39 +7007,39 @@ orphanDependents: false
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -7291,8 +7066,7 @@ orphanDependents: false
kubectl Command
-$ kubectl get job example-job -o json
-
+$ kubectl get job example-job -o json
curl Command (requires kubectl proxy to be running)
@@ -7300,7 +7074,6 @@ $ kubectl get job example-
$ kubectl proxy$ curl -X GET http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs/example-job
-
object name and auth scope, such as for teams and projects
@@ -7458,15 +7229,15 @@ $ kubectl proxy
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -7491,8 +7262,7 @@ $ kubectl proxy
kubectl Command
-$ kubectl get job -o json
-
+$ kubectl get job -o json
curl Command (requires kubectl proxy to be running)
@@ -7500,7 +7270,6 @@ $ kubectl get job -o
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs'
-
Output
@@ -7570,7 +7339,6 @@ $
kubectl proxy
}
]
}
-
Response Body
@@ -7640,7 +7408,6 @@ $ kubectl proxy
}
]
}
-
list or watch objects of kind Job
HTTP Request
@@ -7655,7 +7422,7 @@ $ kubectl proxy
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -7670,39 +7437,39 @@ $ kubectl proxy
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -7728,28 +7495,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Job
HTTP Request
@@ -7764,39 +7527,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -7821,8 +7584,7 @@ $ kubectl proxy
kubectl Command
-$ kubectl get job example-job --watch -o json
-
+$ kubectl get job example-job --watch -o json
curl Command (requires kubectl proxy to be running)
@@ -7830,7 +7592,6 @@ $ kubectl get job example-
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/watch/namespaces/default/jobs/example-job'
-
Output
@@ -7897,7 +7658,6 @@ $
kubectl proxy
}
}
}
-
Response Body
@@ -7964,7 +7724,6 @@ $ kubectl proxy
}
}
}
-
watch changes to an object of kind Job
HTTP Request
@@ -7979,11 +7738,11 @@ $ kubectl proxy
-
name
+
name
name of the Job
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -7998,39 +7757,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -8056,28 +7815,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Job
HTTP Request
@@ -8092,7 +7847,7 @@ $ kubectl proxy
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -8107,39 +7862,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -8165,28 +7920,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Job
HTTP Request
@@ -8201,39 +7952,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -8261,28 +8012,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified Job
HTTP Request
@@ -8297,11 +8044,11 @@ $ kubectl proxy
-
name
+
name
name of the Job
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
Optional duration in seconds the pod may be active on the node relative to StartTime before the system will actively try to mark it failed and kill associated containers. Value must be a positive integer.
AutomountServiceAccountToken indicates whether a service account token should be automatically mounted.
-
containers Container array patch type: merge patch merge key: name
+
containers Container array patch type: merge patch merge key: name
List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod. Cannot be updated.
Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy.
-
dnsPolicy string
+
dnsPolicy string
Set DNS policy for the pod. Defaults to "ClusterFirst". Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to 'ClusterFirstWithHostNet'.
-
hostAliases HostAlias array patch type: merge patch merge key: ip
+
hostAliases HostAlias array patch type: merge patch merge key: ip
HostAliases is an optional list of hosts and IPs that will be injected into the pod's hosts file if specified. This is only valid for non-hostNetwork pods.
-
hostIPC boolean
+
hostIPC boolean
Use the host's ipc namespace. Optional: Default to false.
-
hostNetwork boolean
+
hostNetwork boolean
Host networking requested for this pod. Use the host's network namespace. If this option is set, the ports that will be used must be specified. Default to false.
-
hostPID boolean
+
hostPID boolean
Use the host's pid namespace. Optional: Default to false.
-
hostname string
+
hostname string
Specifies the hostname of the Pod If not specified, the pod's hostname will be set to a system-defined value.
-
imagePullSecrets LocalObjectReference array patch type: merge patch merge key: name
+
imagePullSecrets LocalObjectReference array patch type: merge patch merge key: name
ImagePullSecrets is an optional list of references to secrets in the same namespace to use for pulling any of the images used by this PodSpec. If specified, these secrets will be passed to individual puller implementations for them to use. For example, in the case of docker, only DockerConfig type secrets are honored. More info: https://kubernetes.io/docs/concepts/containers/images#specifying-imagepullsecrets-on-a-pod
-
initContainers Container array patch type: merge patch merge key: name
+
initContainers Container array patch type: merge patch merge key: name
List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, or Liveness probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
-
nodeName string
+
nodeName string
NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.
The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.
-
priorityClassName string
+
priorityClassName string
If specified, indicates the pod's priority. "system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.
SecurityContext holds pod-level security attributes and common container settings. Optional: Defaults to empty. See type description for default values of each field.
-
serviceAccount string
+
serviceAccount string
DeprecatedServiceAccount is a depreciated alias for ServiceAccountName. Deprecated: Use serviceAccountName instead.
Share a single process namespace between all of the containers in a pod. When this is set containers will be able to view and signal processes from other containers in the same pod, and the first process in each container will not be assigned PID 1. HostPID and ShareProcessNamespace cannot both be set. Optional: Default to false. This field is alpha-level and is honored only by servers that enable the PodShareProcessNamespace feature.
-
subdomain string
+
subdomain string
If specified, the fully qualified Pod hostname will be "<hostname>.<subdomain>.<pod namespace>.svc.<cluster domain>". If not specified, the pod will not have a domainname at all.
-
terminationGracePeriodSeconds integer
+
terminationGracePeriodSeconds integer
Optional duration in seconds the pod needs to terminate gracefully. May be decreased in delete request. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period will be used instead. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. Defaults to 30 seconds.
A human readable message indicating details about why the pod is in this condition.
-
nominatedNodeName string
+
nominatedNodeName string
nominatedNodeName is set only when this pod preempts other pods on the node, but it cannot be scheduled right away as preemption victims receive their graceful termination periods. This field does not guarantee that the pod will be scheduled on this node. Scheduler may decide to place the pod elsewhere if other nodes become available sooner. Scheduler may also decide to give the resources on this node to a higher priority pod that is created after preemption. As a result, this field may be different than PodSpec.nodeName when the pod is scheduled.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a Pod
HTTP Request
@@ -9288,11 +9003,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -9307,19 +9022,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of Pod
HTTP Request
@@ -9396,7 +9107,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -9411,39 +9122,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -9471,28 +9182,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified Pod
HTTP Request
@@ -9507,11 +9214,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -9526,15 +9233,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -9560,28 +9267,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Pod
HTTP Request
@@ -9596,7 +9299,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -9611,39 +9314,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -9669,28 +9372,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Pod
HTTP Request
@@ -9705,39 +9404,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -9763,28 +9462,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind Pod
HTTP Request
@@ -9799,11 +9494,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -9818,39 +9513,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -9876,28 +9571,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Pod
HTTP Request
@@ -9912,7 +9603,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -9927,39 +9618,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -9985,28 +9676,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Pod
HTTP Request
@@ -10021,39 +9708,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -10081,28 +9768,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified Pod
HTTP Request
@@ -10117,11 +9800,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect POST requests to portforward of Pod
HTTP Request
@@ -10396,11 +10067,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -10415,7 +10086,7 @@ Appears In:
-
ports
+
ports
List of ports to forward Required when using WebSockets
@@ -10441,28 +10112,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect POST requests to proxy of Pod
HTTP Request
@@ -10477,11 +10144,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -10496,7 +10163,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -10522,28 +10189,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect POST requests to proxy of Pod
HTTP Request
@@ -10558,15 +10221,15 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
-
path
+
path
path to the resource
@@ -10581,7 +10244,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -10607,28 +10270,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect DELETE requests to proxy of Pod
HTTP Request
@@ -10643,11 +10302,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -10662,7 +10321,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -10688,28 +10347,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect DELETE requests to proxy of Pod
HTTP Request
@@ -10724,15 +10379,15 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
-
path
+
path
path to the resource
@@ -10747,7 +10402,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -10773,28 +10428,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect GET requests to portforward of Pod
HTTP Request
@@ -10809,11 +10460,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -10828,7 +10479,7 @@ Appears In:
-
ports
+
ports
List of ports to forward Required when using WebSockets
@@ -10854,28 +10505,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect GET requests to proxy of Pod
HTTP Request
@@ -10890,11 +10537,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -10909,7 +10556,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -10935,28 +10582,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect GET requests to proxy of Pod
HTTP Request
@@ -10971,15 +10614,15 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
-
path
+
path
path to the resource
@@ -10994,7 +10637,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -11020,28 +10663,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect HEAD requests to proxy of Pod
HTTP Request
@@ -11056,11 +10695,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -11075,7 +10714,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -11101,28 +10740,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect HEAD requests to proxy of Pod
HTTP Request
@@ -11137,15 +10772,15 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
-
path
+
path
path to the resource
@@ -11160,7 +10795,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -11186,28 +10821,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect PUT requests to proxy of Pod
HTTP Request
@@ -11222,11 +10853,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -11241,7 +10872,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -11267,28 +10898,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
connect PUT requests to proxy of Pod
HTTP Request
@@ -11303,15 +10930,15 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
-
path
+
path
path to the resource
@@ -11326,7 +10953,7 @@ Appears In:
-
path
+
path
Path is the URL path to use for the current proxy request to pod.
@@ -11354,28 +10981,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read log of the specified Pod
HTTP Request
@@ -11390,11 +11013,11 @@ Appears In:
-
name
+
name
name of the Pod
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -11409,35 +11032,35 @@ Appears In:
-
container
+
container
The container for which to stream logs. Defaults to only container if there is one container in the pod.
-
follow
+
follow
Follow the log stream of the pod. Defaults to false.
-
limitBytes
+
limitBytes
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.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
previous
+
previous
Return previous terminated container logs. Defaults to false.
-
sinceSeconds
+
sinceSeconds
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.
-
tailLines
+
tailLines
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
-
timestamps
+
timestamps
If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false.
@@ -11458,7 +11081,7 @@ Appears In:
-
ReplicaSet v1 apps
+
ReplicaSet [apps/v1]
ReplicaSet Config to run 3 nginx instances.
@@ -11480,8 +11103,6 @@ Appears In:
# Run the nginx image - name:nginx image:nginx:1.10
-
-
ReplicaSet Config to run 3 nginx instances.
@@ -11504,8 +11125,6 @@ Appears In:
# Run the nginx image - name:nginx image:nginx:1.10
-
-
Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a ReplicaSet
HTTP Request
@@ -12010,11 +11613,11 @@ Appears In:
-
name
+
name
name of the ReplicaSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -12029,19 +11632,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of ReplicaSet
HTTP Request
@@ -12118,7 +11717,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -12133,39 +11732,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -12193,28 +11792,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified ReplicaSet
HTTP Request
@@ -12229,11 +11824,11 @@ Appears In:
-
name
+
name
name of the ReplicaSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -12248,15 +11843,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -12282,28 +11877,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ReplicaSet
HTTP Request
@@ -12318,7 +11909,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -12333,39 +11924,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -12391,28 +11982,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ReplicaSet
HTTP Request
@@ -12427,39 +12014,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -12485,28 +12072,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind ReplicaSet
HTTP Request
@@ -12521,11 +12104,11 @@ Appears In:
-
name
+
name
name of the ReplicaSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -12540,39 +12123,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -12598,28 +12181,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ReplicaSet
HTTP Request
@@ -12634,7 +12213,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -12649,39 +12228,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -12707,28 +12286,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ReplicaSet
HTTP Request
@@ -12743,39 +12318,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -12803,28 +12378,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified ReplicaSet
HTTP Request
@@ -12839,11 +12410,11 @@ Appears In:
-
name
+
name
name of the ReplicaSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)
Selector is a label query over pods that should match the Replicas count. If Selector is empty, it is defaulted to the labels present on the Pod template. Label keys and values that must match in order to be controlled by this replication controller, if empty defaulted to labels on Pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a ReplicationController
HTTP Request
@@ -13906,11 +13437,11 @@ Appears In:
-
name
+
name
name of the ReplicationController
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -13925,19 +13456,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of ReplicationController
HTTP Request
@@ -14014,7 +13541,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -14029,39 +13556,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -14089,28 +13616,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified ReplicationController
HTTP Request
@@ -14125,11 +13648,11 @@ Appears In:
-
name
+
name
name of the ReplicationController
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -14144,15 +13667,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -14178,28 +13701,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ReplicationController
HTTP Request
@@ -14214,7 +13733,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -14229,39 +13748,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -14287,28 +13806,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ReplicationController
HTTP Request
@@ -14323,39 +13838,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -14381,28 +13896,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind ReplicationController
HTTP Request
@@ -14417,11 +13928,11 @@ Appears In:
-
name
+
name
name of the ReplicationController
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -14436,39 +13947,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -14494,28 +14005,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ReplicationController
HTTP Request
@@ -14530,7 +14037,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -14545,39 +14052,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -14603,28 +14110,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ReplicationController
HTTP Request
@@ -14639,39 +14142,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -14699,28 +14202,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified ReplicationController
HTTP Request
@@ -14735,11 +14234,11 @@ Appears In:
-
name
+
name
name of the ReplicationController
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.
@@ -15330,35 +14809,35 @@ Appears In:
-
podManagementPolicy string
+
podManagementPolicy string
podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is OrderedReady, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is Parallel which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.
-
replicas integer
+
replicas integer
replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.
-
revisionHistoryLimit integer
+
revisionHistoryLimit integer
revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet's revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.
serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where "pod-specific-string" is managed by the StatefulSet controller.
template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.
volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.
@@ -15380,39 +14859,39 @@ Appears In:
-
collisionCount integer
+
collisionCount integer
collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
Represents the latest available observations of a statefulset's current state.
-
currentReplicas integer
+
currentReplicas integer
currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.
-
currentRevision string
+
currentRevision string
currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).
-
observedGeneration integer
+
observedGeneration integer
observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet's generation, which is updated on mutation by the API Server.
-
readyReplicas integer
+
readyReplicas integer
readyReplicas is the number of Pods created by the StatefulSet controller that have a Ready Condition.
-
replicas integer
+
replicas integer
replicas is the number of Pods created by the StatefulSet controller.
-
updateRevision string
+
updateRevision string
updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)
-
updatedReplicas integer
+
updatedReplicas integer
updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a StatefulSet
HTTP Request
@@ -15784,11 +15247,11 @@ Appears In:
-
name
+
name
name of the StatefulSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -15803,19 +15266,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of StatefulSet
HTTP Request
@@ -15892,7 +15351,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -15907,39 +15366,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -15967,28 +15426,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified StatefulSet
HTTP Request
@@ -16003,11 +15458,11 @@ Appears In:
-
name
+
name
name of the StatefulSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -16022,15 +15477,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -16056,28 +15511,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind StatefulSet
HTTP Request
@@ -16092,7 +15543,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -16107,39 +15558,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -16165,28 +15616,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind StatefulSet
HTTP Request
@@ -16201,39 +15648,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -16259,28 +15706,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind StatefulSet
HTTP Request
@@ -16295,11 +15738,11 @@ Appears In:
-
name
+
name
name of the StatefulSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -16314,39 +15757,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -16372,28 +15815,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of StatefulSet
HTTP Request
@@ -16408,7 +15847,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -16423,39 +15862,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -16481,28 +15920,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of StatefulSet
HTTP Request
@@ -16517,39 +15952,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -16577,28 +16012,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified StatefulSet
HTTP Request
@@ -16613,11 +16044,11 @@ Appears In:
-
name
+
name
name of the StatefulSet
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
The set of all endpoints is the union of all subsets. Addresses are placed into subsets according to the IPs they share. A single address with multiple ports, some of which are ready and some of which are not (because they come from different containers) will result in the address being displayed in different subsets for the different ports. No address will appear in both Addresses and NotReadyAddresses in the same subset. Sets of addresses and ports that comprise a service.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete Endpoints
HTTP Request
@@ -17568,11 +16963,11 @@ Appears In:
-
name
+
name
name of the Endpoints
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -17587,19 +16982,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of Endpoints
HTTP Request
@@ -17676,7 +17067,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -17691,39 +17082,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -17751,28 +17142,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified Endpoints
HTTP Request
@@ -17787,11 +17174,11 @@ Appears In:
-
name
+
name
name of the Endpoints
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -17806,15 +17193,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -17840,28 +17227,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Endpoints
HTTP Request
@@ -17876,7 +17259,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -17891,39 +17274,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -17949,28 +17332,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Endpoints
HTTP Request
@@ -17985,39 +17364,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -18043,28 +17422,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind Endpoints
HTTP Request
@@ -18079,11 +17454,11 @@ Appears In:
-
name
+
name
name of the Endpoints
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -18098,39 +17473,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -18156,28 +17531,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Endpoints
HTTP Request
@@ -18192,7 +17563,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -18207,39 +17578,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -18265,28 +17636,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Endpoints
HTTP Request
@@ -18301,39 +17668,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
A default backend capable of servicing requests that don't match any rule. At least one of 'backend' or 'rules' must be specified. This field is optional to allow the loadbalancer controller or defaulting logic to specify a global default.
TLS configuration. Currently the Ingress only supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the hostname specified through the SNI TLS extension, if the ingress controller fulfilling the ingress supports SNI.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete an Ingress
HTTP Request
@@ -18828,11 +18179,11 @@ Appears In:
-
name
+
name
name of the Ingress
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -18847,19 +18198,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of Ingress
HTTP Request
@@ -18936,7 +18283,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -18951,39 +18298,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -19011,28 +18358,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified Ingress
HTTP Request
@@ -19047,11 +18390,11 @@ Appears In:
-
name
+
name
name of the Ingress
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -19066,15 +18409,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -19100,28 +18443,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Ingress
HTTP Request
@@ -19136,7 +18475,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -19151,39 +18490,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -19209,28 +18548,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Ingress
HTTP Request
@@ -19245,39 +18580,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -19303,28 +18638,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind Ingress
HTTP Request
@@ -19339,11 +18670,11 @@ Appears In:
-
name
+
name
name of the Ingress
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -19358,39 +18689,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -19416,28 +18747,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Ingress
HTTP Request
@@ -19452,7 +18779,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -19467,39 +18794,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -19525,28 +18852,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Ingress
HTTP Request
@@ -19561,39 +18884,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -19621,28 +18944,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified Ingress
HTTP Request
@@ -19657,11 +18976,11 @@ Appears In:
-
name
+
name
name of the Ingress
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
Service Config to load balance traffic across all Pods with the app=nginx label. Receives on and sends to port 80. Exposes an externally accessible endpoint.
@@ -19917,8 +19228,6 @@ spec:
# with an External IP address - *Only supported
# by some cloud providers*
type: LoadBalancer
-
-
Service Config to load balance traffic across all Pods with the app=nginx label. Receives on and sends to port 80. Exposes an externally accessible endpoint.
@@ -19943,8 +19252,6 @@ spec:
# with an External IP address - *Only supported
# by some cloud providers*
type: LoadBalancer
-
-
clusterIP is the IP address of the service and is usually assigned randomly by the master. If an address is specified manually and is not in use by others, it will be allocated to the service; otherwise, creation of the service will fail. This field can not be changed through updates. Valid values are "None", empty string (""), or a valid IP address. "None" can be specified for headless services when proxying is not required. Only applies to types ClusterIP, NodePort, and LoadBalancer. Ignored if type is ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
-
externalIPs string array
+
externalIPs string array
externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. The user is responsible for ensuring that traffic arrives at a node with this IP. A common example is external load-balancers that are not part of the Kubernetes system.
-
externalName string
+
externalName string
externalName is the external reference that kubedns or equivalent will return as a CNAME record for this service. No proxying will be involved. Must be a valid RFC-1123 hostname (https://tools.ietf.org/html/rfc1123) and requires Type to be ExternalName.
-
externalTrafficPolicy string
+
externalTrafficPolicy string
externalTrafficPolicy denotes if this Service desires to route external traffic to node-local or cluster-wide endpoints. "Local" preserves the client source IP and avoids a second hop for LoadBalancer and Nodeport type services, but risks potentially imbalanced traffic spreading. "Cluster" obscures the client source IP and may cause a second hop to another node, but should have good overall load-spreading.
-
healthCheckNodePort integer
+
healthCheckNodePort integer
healthCheckNodePort specifies the healthcheck nodePort for the service. If not specified, HealthCheckNodePort is created by the service api backend with the allocated nodePort. Will use user-specified nodePort value if specified by the client. Only effects when Type is set to LoadBalancer and ExternalTrafficPolicy is set to Local.
-
loadBalancerIP string
+
loadBalancerIP string
Only applies to Service Type: LoadBalancer LoadBalancer will get created with the IP specified in this field. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature.
publishNotReadyAddresses, when set to true, indicates that DNS implementations must publish the notReadyAddresses of subsets for the Endpoints associated with the Service. The default value is false. The primary use case for setting this field is to use a StatefulSet's Headless Service to propagate SRV records for its Pods without respect to their readiness for purpose of peer discovery. This field will replace the service.alpha.kubernetes.io/tolerate-unready-endpoints when that annotation is deprecated and all clients have been converted to use this field.
-
selector object
+
selector object
Route service traffic to pods with label keys and values matching this selector. If empty or not present, the service is assumed to have an external process managing its endpoints, which Kubernetes will not modify. Only applies to types ClusterIP, NodePort, and LoadBalancer. Ignored if type is ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/
sessionAffinityConfig contains the configurations of session affinity.
-
type string
+
type string
type determines how the Service is exposed. Defaults to ClusterIP. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. "ExternalName" maps to the specified externalName. "ClusterIP" allocates a cluster-internal IP address for load-balancing to endpoints. Endpoints are determined by the selector or if that is not specified, by manual construction of an Endpoints object. If clusterIP is "None", no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a stable IP. "NodePort" builds on ClusterIP and allocates a port on every node which routes to the clusterIP. "LoadBalancer" builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the clusterIP. More info: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services---service-types
@@ -20641,11 +19931,11 @@ service "deployment-example" deleted
-
name
+
name
name of the Service
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -20660,19 +19950,19 @@ service "deployment-example" deleted
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
@@ -20687,7 +19977,7 @@ service "deployment-example" deleted
object name and auth scope, such as for teams and projects
@@ -20845,15 +20131,15 @@ $ curl -X GET http://
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -20879,7 +20165,6 @@ $ curl -X GET http://
$ kubectl get service -o json
-
curl Command (requires kubectl proxy to be running)
@@ -20887,21 +20172,16 @@ $ kubectl get
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/api/v1/namespaces/default/services'
-
Output
-
-
Response Body
-
-
list or watch objects of kind Service
HTTP Request
@@ -20916,7 +20196,7 @@ $ kubectl proxy
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -20931,39 +20211,39 @@ $
kubectl proxy
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -20989,28 +20269,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Service
HTTP Request
@@ -21025,39 +20301,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -21083,7 +20359,6 @@ $ kubectl proxy
$ kubectl get service deployment-example --watch -o json
-
curl Command (requires kubectl proxy to be running)
@@ -21091,7 +20366,6 @@ $ kubectl get
$ kubectl proxy$ curl -X GET 'http://127.0.0.1:8001/api/v1/watch/namespaces/default/services/deployment-example'
-
Output
@@ -21138,7 +20412,6 @@ $
kubectl proxy
}
}
}
-
Response Body
@@ -21185,7 +20458,6 @@ $ kubectl proxy
}
}
}
-
watch changes to an object of kind Service
HTTP Request
@@ -21200,11 +20472,11 @@ $ kubectl proxy
-
name
+
name
name of the Service
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -21219,39 +20491,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -21277,28 +20549,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Service
HTTP Request
@@ -21313,7 +20581,7 @@ $ kubectl proxy
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -21328,39 +20596,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -21386,28 +20654,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Service
HTTP Request
@@ -21422,39 +20686,39 @@ $ kubectl proxy
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -21482,28 +20746,24 @@ $ kubectl proxy
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified Service
HTTP Request
@@ -21518,11 +20778,11 @@ $ kubectl proxy
-
name
+
name
name of the Service
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
BinaryData contains the binary data. Each key must consist of alphanumeric characters, '-', '_' or '.'. BinaryData can contain byte sequences that are not in the UTF-8 range. The keys stored in BinaryData must not overlap with the ones in the Data field, this is enforced during validation process. Using this field will require 1.10+ apiserver and kubelet.
-
data object
+
data object
Data contains the configuration data. Each key must consist of alphanumeric characters, '-', '_' or '.'. Values with non-UTF-8 byte sequences must use the BinaryData field. The keys stored in Data must not overlap with the keys in the BinaryData field, this is enforced during validation process.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a ConfigMap
HTTP Request
@@ -23017,11 +22213,11 @@ Appears In:
-
name
+
name
name of the ConfigMap
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -23036,19 +22232,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of ConfigMap
HTTP Request
@@ -23125,7 +22317,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -23140,39 +22332,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -23200,28 +22392,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified ConfigMap
HTTP Request
@@ -23236,11 +22424,11 @@ Appears In:
-
name
+
name
name of the ConfigMap
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -23255,15 +22443,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -23289,28 +22477,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ConfigMap
HTTP Request
@@ -23325,7 +22509,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -23340,39 +22524,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -23398,28 +22582,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ConfigMap
HTTP Request
@@ -23434,39 +22614,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -23492,28 +22672,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind ConfigMap
HTTP Request
@@ -23528,11 +22704,11 @@ Appears In:
-
name
+
name
name of the ConfigMap
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -23547,39 +22723,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -23605,28 +22781,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ConfigMap
HTTP Request
@@ -23641,7 +22813,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -23656,39 +22828,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -23714,28 +22886,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ConfigMap
HTTP Request
@@ -23750,39 +22918,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Data contains the secret data. Each key must consist of alphanumeric characters, '-', '_' or '.'. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4
stringData allows specifying non-binary secret data in string form. It is provided as a write-only convenience method. All keys and values are merged into the data field on write, overwriting any existing values. It is never output when reading from the API.
-
type string
+
type string
Used to facilitate programmatic handling of secret data.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a Secret
HTTP Request
@@ -24229,11 +23381,11 @@ Appears In:
-
name
+
name
name of the Secret
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -24248,19 +23400,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of Secret
HTTP Request
@@ -24337,7 +23485,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -24352,39 +23500,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -24412,28 +23560,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified Secret
HTTP Request
@@ -24448,11 +23592,11 @@ Appears In:
-
name
+
name
name of the Secret
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -24467,15 +23611,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -24501,28 +23645,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Secret
HTTP Request
@@ -24537,7 +23677,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -24552,39 +23692,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -24610,28 +23750,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Secret
HTTP Request
@@ -24646,39 +23782,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -24704,28 +23840,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind Secret
HTTP Request
@@ -24740,11 +23872,11 @@ Appears In:
-
name
+
name
name of the Secret
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -24759,39 +23891,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -24817,28 +23949,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Secret
HTTP Request
@@ -24853,7 +23981,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -24868,39 +23996,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -24926,28 +24054,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Secret
HTTP Request
@@ -24962,39 +24086,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec. This is an alpha feature and may change in the future.
-
volumeName string
+
volumeName string
VolumeName is the binding reference to the PersistentVolume backing this claim.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a PersistentVolumeClaim
HTTP Request
@@ -25521,11 +24629,11 @@ Appears In:
-
name
+
name
name of the PersistentVolumeClaim
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -25540,19 +24648,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of PersistentVolumeClaim
HTTP Request
@@ -25629,7 +24733,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -25644,39 +24748,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -25704,28 +24808,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified PersistentVolumeClaim
HTTP Request
@@ -25740,11 +24840,11 @@ Appears In:
-
name
+
name
name of the PersistentVolumeClaim
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -25759,15 +24859,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -25793,28 +24893,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PersistentVolumeClaim
HTTP Request
@@ -25829,7 +24925,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -25844,39 +24940,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -25902,28 +24998,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PersistentVolumeClaim
HTTP Request
@@ -25938,39 +25030,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -25996,28 +25088,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind PersistentVolumeClaim
HTTP Request
@@ -26032,11 +25120,11 @@ Appears In:
-
name
+
name
name of the PersistentVolumeClaim
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -26051,39 +25139,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -26109,28 +25197,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PersistentVolumeClaim
HTTP Request
@@ -26145,7 +25229,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -26160,39 +25244,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -26218,28 +25302,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PersistentVolumeClaim
HTTP Request
@@ -26254,39 +25334,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -26314,28 +25394,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified PersistentVolumeClaim
HTTP Request
@@ -26350,11 +25426,11 @@ Appears In:
-
name
+
name
name of the PersistentVolumeClaim
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. ["ro", "soft"]. Not validated - mount of the PVs will simply fail if one is invalid.
-
parameters object
+
parameters object
Parameters holds the parameters for the provisioner that should create volumes of this storage class.
-
provisioner string
+
provisioner string
Provisioner indicates the type of the provisioner.
-
reclaimPolicy string
+
reclaimPolicy string
Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.
-
volumeBindingMode string
+
volumeBindingMode string
VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound. When unset, VolumeBindingImmediate is used. This field is alpha-level and is only honored by servers that enable the VolumeScheduling feature.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a StorageClass
HTTP Request
@@ -27005,7 +26057,7 @@ Appears In:
-
name
+
name
name of the StorageClass
@@ -27020,19 +26072,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of StorageClass
HTTP Request
@@ -27109,39 +26157,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -27169,28 +26217,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified StorageClass
HTTP Request
@@ -27205,7 +26249,7 @@ Appears In:
-
name
+
name
name of the StorageClass
@@ -27220,15 +26264,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -27254,28 +26298,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind StorageClass
HTTP Request
@@ -27290,39 +26330,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -27348,28 +26388,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind StorageClass
HTTP Request
@@ -27384,7 +26420,7 @@ Appears In:
-
name
+
name
name of the StorageClass
@@ -27399,39 +26435,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -27457,28 +26493,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of StorageClass
HTTP Request
@@ -27493,39 +26525,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
HostPath represents a pre-existing file or directory on the host machine that is directly exposed to the container. This is generally used for system agents or other privileged things that are allowed to see the host machine. Most containers will NOT need this. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath
The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
-
attached boolean
+
attached boolean
Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
-
attachmentMetadata object
+
attachmentMetadata object
Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.
The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a VolumeAttachment
HTTP Request
@@ -28162,7 +27178,7 @@ Appears In:
-
name
+
name
name of the VolumeAttachment
@@ -28177,19 +27193,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of VolumeAttachment
HTTP Request
@@ -28266,39 +27278,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -28326,28 +27338,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified VolumeAttachment
HTTP Request
@@ -28362,7 +27370,7 @@ Appears In:
-
name
+
name
name of the VolumeAttachment
@@ -28377,15 +27385,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -28411,28 +27419,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind VolumeAttachment
HTTP Request
@@ -28447,39 +27451,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -28505,28 +27509,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind VolumeAttachment
HTTP Request
@@ -28541,7 +27541,7 @@ Appears In:
-
name
+
name
name of the VolumeAttachment
@@ -28556,39 +27556,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -28614,28 +27614,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of VolumeAttachment
HTTP Request
@@ -28650,39 +27646,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a ControllerRevision
HTTP Request
@@ -29138,11 +28118,11 @@ Appears In:
-
name
+
name
name of the ControllerRevision
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -29157,19 +28137,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of ControllerRevision
HTTP Request
@@ -29246,7 +28222,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -29261,39 +28237,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -29321,28 +28297,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified ControllerRevision
HTTP Request
@@ -29357,11 +28329,11 @@ Appears In:
-
name
+
name
name of the ControllerRevision
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -29376,15 +28348,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -29410,28 +28382,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ControllerRevision
HTTP Request
@@ -29446,7 +28414,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -29461,39 +28429,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -29519,28 +28487,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ControllerRevision
HTTP Request
@@ -29555,39 +28519,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -29613,28 +28577,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind ControllerRevision
HTTP Request
@@ -29649,11 +28609,11 @@ Appears In:
-
name
+
name
name of the ControllerRevision
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -29668,39 +28628,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -29726,28 +28686,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ControllerRevision
HTTP Request
@@ -29762,7 +28718,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -29777,39 +28733,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -29835,28 +28791,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ControllerRevision
HTTP Request
@@ -29871,39 +28823,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Subresources describes the subresources for CustomResources This field is alpha-level and should only be sent to servers that enable subresources via the CustomResourceSubresources feature gate.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a CustomResourceDefinition
HTTP Request
@@ -30391,7 +29327,7 @@ Appears In:
-
name
+
name
name of the CustomResourceDefinition
@@ -30406,19 +29342,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of CustomResourceDefinition
HTTP Request
@@ -30495,39 +29427,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -30555,28 +29487,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified CustomResourceDefinition
HTTP Request
@@ -30591,7 +29519,7 @@ Appears In:
-
name
+
name
name of the CustomResourceDefinition
@@ -30606,15 +29534,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -30640,28 +29568,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind CustomResourceDefinition
HTTP Request
@@ -30676,39 +29600,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -30734,28 +29658,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind CustomResourceDefinition
HTTP Request
@@ -30770,7 +29690,7 @@ Appears In:
-
name
+
name
name of the CustomResourceDefinition
@@ -30785,39 +29705,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -30843,28 +29763,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of CustomResourceDefinition
HTTP Request
@@ -30879,39 +29795,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -30939,28 +29855,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
replace status of the specified CustomResourceDefinition
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete an Event
HTTP Request
@@ -31503,11 +30399,11 @@ Appears In:
-
name
+
name
name of the Event
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -31522,19 +30418,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of Event
HTTP Request
@@ -31611,7 +30503,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -31626,39 +30518,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -31686,28 +30578,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified Event
HTTP Request
@@ -31722,11 +30610,11 @@ Appears In:
-
name
+
name
name of the Event
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -31741,15 +30629,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -31775,28 +30663,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Event
HTTP Request
@@ -31811,7 +30695,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -31826,39 +30710,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -31884,28 +30768,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind Event
HTTP Request
@@ -31920,39 +30800,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -31978,28 +30858,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind Event
HTTP Request
@@ -32014,11 +30890,11 @@ Appears In:
-
name
+
name
name of the Event
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -32033,39 +30909,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -32091,28 +30967,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Event
HTTP Request
@@ -32127,7 +30999,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -32142,39 +31014,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -32200,28 +31072,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of Event
HTTP Request
@@ -32236,39 +31104,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a LimitRange
HTTP Request
@@ -32729,11 +31581,11 @@ Appears In:
-
name
+
name
name of the LimitRange
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -32748,19 +31600,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of LimitRange
HTTP Request
@@ -32837,7 +31685,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -32852,39 +31700,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -32912,28 +31760,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified LimitRange
HTTP Request
@@ -32948,11 +31792,11 @@ Appears In:
-
name
+
name
name of the LimitRange
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -32967,15 +31811,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -33001,28 +31845,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind LimitRange
HTTP Request
@@ -33037,7 +31877,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -33052,39 +31892,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -33110,28 +31950,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind LimitRange
HTTP Request
@@ -33146,39 +31982,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -33204,28 +32040,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind LimitRange
HTTP Request
@@ -33240,11 +32072,11 @@ Appears In:
-
name
+
name
name of the LimitRange
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -33259,39 +32091,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -33317,28 +32149,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of LimitRange
HTTP Request
@@ -33353,7 +32181,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -33368,39 +32196,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -33426,28 +32254,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of LimitRange
HTTP Request
@@ -33462,39 +32286,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
reference to scaled resource; horizontal pod autoscaler will learn the current resource consumption and will set the desired number of pods by using its Scale subresource.
-
targetCPUUtilizationPercentage integer
+
targetCPUUtilizationPercentage integer
target average CPU utilization (represented as a percentage of requested CPU) over all the pods; if not specified the default autoscaling policy will be used.
@@ -33624,23 +32448,23 @@ Appears In:
-
currentCPUUtilizationPercentage integer
+
currentCPUUtilizationPercentage integer
current average CPU utilization over all pods, represented as a percentage of requested CPU, e.g. 70 means that an average pod is using now 70% of its requested CPU.
-
currentReplicas integer
+
currentReplicas integer
current number of replicas of pods managed by this autoscaler.
-
desiredReplicas integer
+
desiredReplicas integer
desired number of replicas of pods managed by this autoscaler.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a HorizontalPodAutoscaler
HTTP Request
@@ -34012,11 +32820,11 @@ Appears In:
-
name
+
name
name of the HorizontalPodAutoscaler
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -34031,19 +32839,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of HorizontalPodAutoscaler
HTTP Request
@@ -34120,7 +32924,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -34135,39 +32939,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -34195,28 +32999,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified HorizontalPodAutoscaler
HTTP Request
@@ -34231,11 +33031,11 @@ Appears In:
-
name
+
name
name of the HorizontalPodAutoscaler
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -34250,15 +33050,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -34284,28 +33084,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind HorizontalPodAutoscaler
HTTP Request
@@ -34320,7 +33116,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -34335,39 +33131,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -34393,28 +33189,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind HorizontalPodAutoscaler
HTTP Request
@@ -34429,39 +33221,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -34487,28 +33279,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind HorizontalPodAutoscaler
HTTP Request
@@ -34523,11 +33311,11 @@ Appears In:
-
name
+
name
name of the HorizontalPodAutoscaler
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -34542,39 +33330,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -34600,28 +33388,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of HorizontalPodAutoscaler
HTTP Request
@@ -34636,7 +33420,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -34651,39 +33435,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -34709,28 +33493,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of HorizontalPodAutoscaler
HTTP Request
@@ -34745,39 +33525,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -34805,28 +33585,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified HorizontalPodAutoscaler
HTTP Request
@@ -34841,11 +33617,11 @@ Appears In:
-
name
+
name
name of the HorizontalPodAutoscaler
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
initializers Initializer array patch type: merge patch merge key: name
+
initializers Initializer array patch type: merge patch merge key: name
Initializers is a list of resources and their default initializers Order-sensitive. When merging multiple InitializerConfigurations, we sort the initializers from different InitializerConfigurations by the name of the InitializerConfigurations; the order of the initializers from the same InitializerConfiguration is preserved.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete an InitializerConfiguration
HTTP Request
@@ -35472,7 +34224,7 @@ Appears In:
-
name
+
name
name of the InitializerConfiguration
@@ -35487,19 +34239,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of InitializerConfiguration
HTTP Request
@@ -35576,39 +34324,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -35636,28 +34384,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified InitializerConfiguration
HTTP Request
@@ -35672,7 +34416,7 @@ Appears In:
-
name
+
name
name of the InitializerConfiguration
@@ -35687,15 +34431,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -35721,28 +34465,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind InitializerConfiguration
HTTP Request
@@ -35757,39 +34497,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -35815,28 +34555,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind InitializerConfiguration
HTTP Request
@@ -35851,7 +34587,7 @@ Appears In:
-
name
+
name
name of the InitializerConfiguration
@@ -35866,39 +34602,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -35924,28 +34660,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of InitializerConfiguration
HTTP Request
@@ -35960,39 +34692,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a MutatingWebhookConfiguration
HTTP Request
@@ -36408,7 +35124,7 @@ Appears In:
-
name
+
name
name of the MutatingWebhookConfiguration
@@ -36423,19 +35139,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of MutatingWebhookConfiguration
HTTP Request
@@ -36512,39 +35224,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -36572,28 +35284,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified MutatingWebhookConfiguration
HTTP Request
@@ -36608,7 +35316,7 @@ Appears In:
-
name
+
name
name of the MutatingWebhookConfiguration
@@ -36623,15 +35331,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -36657,28 +35365,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind MutatingWebhookConfiguration
HTTP Request
@@ -36693,39 +35397,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -36751,28 +35455,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind MutatingWebhookConfiguration
HTTP Request
@@ -36787,7 +35487,7 @@ Appears In:
-
name
+
name
name of the MutatingWebhookConfiguration
@@ -36802,39 +35502,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -36860,28 +35560,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of MutatingWebhookConfiguration
HTTP Request
@@ -36896,39 +35592,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a ValidatingWebhookConfiguration
HTTP Request
@@ -37344,7 +36024,7 @@ Appears In:
-
name
+
name
name of the ValidatingWebhookConfiguration
@@ -37359,19 +36039,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of ValidatingWebhookConfiguration
HTTP Request
@@ -37448,39 +36124,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -37508,28 +36184,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified ValidatingWebhookConfiguration
HTTP Request
@@ -37544,7 +36216,7 @@ Appears In:
-
name
+
name
name of the ValidatingWebhookConfiguration
@@ -37559,15 +36231,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -37593,28 +36265,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind ValidatingWebhookConfiguration
HTTP Request
@@ -37629,39 +36297,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -37687,28 +36355,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind ValidatingWebhookConfiguration
HTTP Request
@@ -37723,7 +36387,7 @@ Appears In:
-
name
+
name
name of the ValidatingWebhookConfiguration
@@ -37738,39 +36402,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -37796,28 +36460,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of ValidatingWebhookConfiguration
HTTP Request
@@ -37832,39 +36492,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a PodTemplate
HTTP Request
@@ -38344,11 +36988,11 @@ Appears In:
-
name
+
name
name of the PodTemplate
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -38363,19 +37007,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of PodTemplate
HTTP Request
@@ -38452,7 +37092,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -38467,39 +37107,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -38527,28 +37167,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified PodTemplate
HTTP Request
@@ -38563,11 +37199,11 @@ Appears In:
-
name
+
name
name of the PodTemplate
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -38582,15 +37218,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -38616,28 +37252,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PodTemplate
HTTP Request
@@ -38652,7 +37284,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -38667,39 +37299,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -38725,28 +37357,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PodTemplate
HTTP Request
@@ -38761,39 +37389,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -38819,28 +37447,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind PodTemplate
HTTP Request
@@ -38855,11 +37479,11 @@ Appears In:
-
name
+
name
name of the PodTemplate
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -38874,39 +37498,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -38932,28 +37556,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PodTemplate
HTTP Request
@@ -38968,7 +37588,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -38983,39 +37603,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -39041,28 +37661,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PodTemplate
HTTP Request
@@ -39077,39 +37693,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Most recently observed status of the PodDisruptionBudget.
@@ -39202,15 +37818,15 @@ Appears In:
-
maxUnavailable
+
maxUnavailable
An eviction is allowed if at most "maxUnavailable" pods selected by "selector" are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with "minAvailable".
-
minAvailable
+
minAvailable
An eviction is allowed if at least "minAvailable" pods selected by "selector" will still be available after the eviction, i.e. even in the absence of the evicted pod. So for example you can prevent all voluntary evictions by specifying "100%".
Label query over pods whose evictions are managed by the disruption budget.
@@ -39232,27 +37848,27 @@ Appears In:
-
currentHealthy integer
+
currentHealthy integer
current number of healthy pods
-
desiredHealthy integer
+
desiredHealthy integer
minimum desired number of healthy pods
-
disruptedPods object
+
disruptedPods object
DisruptedPods contains information about pods whose eviction was processed by the API server eviction subresource handler but has not yet been observed by the PodDisruptionBudget controller. A pod will be in this map from the time when the API server processed the eviction request to the time when the pod is seen by PDB controller as having been marked for deletion (or after a timeout). The key in the map is the name of the pod and the value is the time when the API server processed the eviction request. If the deletion didn't occur and a pod is still there it will be removed from the list automatically by PodDisruptionBudget controller after some time. If everything goes smooth this map should be empty for the most of the time. Large number of entries in the map may indicate problems with pod deletions.
-
disruptionsAllowed integer
+
disruptionsAllowed integer
Number of pod disruptions that are currently allowed.
-
expectedPods integer
+
expectedPods integer
total number of pods counted by this disruption budget
-
observedGeneration integer
+
observedGeneration integer
Most recent generation observed when updating this PDB status. PodDisruptionsAllowed and other status informatio is valid only if observedGeneration equals to PDB's object generation.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a PodDisruptionBudget
HTTP Request
@@ -39624,11 +38224,11 @@ Appears In:
-
name
+
name
name of the PodDisruptionBudget
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -39643,19 +38243,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of PodDisruptionBudget
HTTP Request
@@ -39732,7 +38328,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -39747,39 +38343,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -39807,28 +38403,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified PodDisruptionBudget
HTTP Request
@@ -39843,11 +38435,11 @@ Appears In:
-
name
+
name
name of the PodDisruptionBudget
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -39862,15 +38454,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -39896,28 +38488,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PodDisruptionBudget
HTTP Request
@@ -39932,7 +38520,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -39947,39 +38535,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -40005,28 +38593,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PodDisruptionBudget
HTTP Request
@@ -40041,39 +38625,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -40099,28 +38683,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind PodDisruptionBudget
HTTP Request
@@ -40135,11 +38715,11 @@ Appears In:
-
name
+
name
name of the PodDisruptionBudget
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -40154,39 +38734,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -40212,28 +38792,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PodDisruptionBudget
HTTP Request
@@ -40248,7 +38824,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -40263,39 +38839,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -40321,28 +38897,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PodDisruptionBudget
HTTP Request
@@ -40357,39 +38929,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -40417,28 +38989,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
partially update status of the specified PodDisruptionBudget
HTTP Request
@@ -40453,11 +39021,11 @@ Appears In:
-
name
+
name
name of the PodDisruptionBudget
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
description is an arbitrary string that usually provides guidelines on when this priority class should be used.
-
globalDefault boolean
+
globalDefault boolean
globalDefault specifies whether this PriorityClass should be considered as the default priority for pods that do not have any priority class. Only one PriorityClass can be marked as globalDefault. However, if more than one PriorityClasses exists with their globalDefault field set to true, the smallest value of such global default PriorityClasses will be used as the default priority.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a PriorityClass
HTTP Request
@@ -41098,7 +39642,7 @@ Appears In:
-
name
+
name
name of the PriorityClass
@@ -41113,19 +39657,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of PriorityClass
HTTP Request
@@ -41202,39 +39742,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -41262,28 +39802,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified PriorityClass
HTTP Request
@@ -41298,7 +39834,7 @@ Appears In:
-
name
+
name
name of the PriorityClass
@@ -41313,15 +39849,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -41347,28 +39883,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PriorityClass
HTTP Request
@@ -41383,39 +39915,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -41441,28 +39973,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind PriorityClass
HTTP Request
@@ -41477,7 +40005,7 @@ Appears In:
-
name
+
name
name of the PriorityClass
@@ -41492,39 +40020,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -41550,28 +40078,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PriorityClass
HTTP Request
@@ -41586,39 +40110,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete a PodPreset
HTTP Request
@@ -42101,11 +40609,11 @@ Appears In:
-
name
+
name
name of the PodPreset
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -42120,19 +40628,19 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
gracePeriodSeconds
+
gracePeriodSeconds
The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.
-
orphanDependents
+
orphanDependents
Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.
-
propagationPolicy
+
propagationPolicy
Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
delete collection of PodPreset
HTTP Request
@@ -42209,7 +40713,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -42224,39 +40728,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -42284,28 +40788,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
read the specified PodPreset
HTTP Request
@@ -42320,11 +40820,11 @@ Appears In:
-
name
+
name
name of the PodPreset
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -42339,15 +40839,15 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
exact
+
exact
Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.
-
export
+
export
Should this value be exported. Export strips fields that a user can not specify.
@@ -42373,28 +40873,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PodPreset
HTTP Request
@@ -42409,7 +40905,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -42424,39 +40920,39 @@ Appears In:
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -42482,28 +40978,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
list or watch objects of kind PodPreset
HTTP Request
@@ -42518,39 +41010,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -42576,28 +41068,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch changes to an object of kind PodPreset
HTTP Request
@@ -42612,11 +41100,11 @@ Appears In:
-
name
+
name
name of the PodPreset
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -42631,39 +41119,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -42689,28 +41177,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PodPreset
HTTP Request
@@ -42725,7 +41209,7 @@ Appears In:
-
namespace
+
namespace
object name and auth scope, such as for teams and projects
@@ -42740,39 +41224,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -42798,28 +41282,24 @@ Appears In:
Coming Soon
-
curl Command (requires kubectl proxy to be running)
Coming Soon
-
Output
Coming Soon
-
Response Body
Coming Soon
-
watch individual changes to a list of PodPreset
HTTP Request
@@ -42834,39 +41314,39 @@ Appears In:
-
continue
+
continue
The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-
fieldSelector
+
fieldSelector
A selector to restrict the list of returned objects by their fields. Defaults to everything.
-
includeUninitialized
+
includeUninitialized
If true, partially initialized resources are included in the response.
-
labelSelector
+
labelSelector
A selector to restrict the list of returned objects by their labels. Defaults to everything.
-
limit
+
limit
limit is a maximum number of responses to return for a list call. If more items exist, the server will set the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-
pretty
+
pretty
If 'true', then the output is pretty printed.
-
resourceVersion
+
resourceVersion
When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
-
timeoutSeconds
+
timeoutSeconds
Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-
watch
+
watch
Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
@@ -42887,7 +41367,7 @@ Appears In:
-
PodSecurityPolicy v1beta1 extensions
+
PodSecurityPolicy [extensions/v1beta1]
@@ -42898,13 +41378,13 @@ Appears In:
-
extensions
-
v1beta1
-
PodSecurityPolicy
+
extensions
+
v1beta1
+
PodSecurityPolicy
-
Pod Security Policy governs the ability to make requests that affect the Security Context that will be applied to a pod and container.
+
PodSecurityPolicy governs the ability to make requests that affect the Security Context that will be applied to a pod and container. Deprecated: use PodSecurityPolicy from policy API Group instead.