Kazan v0.9.0 Kazan.Apis.Extensions.V1beta1 View Source
Contains functions for V1beta1 of the Extensions API group.
Each of these functions will output a Kazan.Request
suitable for passing
to Kazan.run
.
This module also contains struct submodules that can be sent & received from this version of the Extensions API.
Link to this section Summary
Functions
create a DaemonSet
create a DaemonSet
create a Deployment
create a Deployment
create rollback of a Deployment
create rollback of a Deployment
create an Ingress
create an Ingress
create a NetworkPolicy
create a NetworkPolicy
create a ReplicaSet
create a ReplicaSet
create a PodSecurityPolicy
create a PodSecurityPolicy
delete collection of DaemonSet
delete collection of DaemonSet
delete collection of Deployment
delete collection of Deployment
delete collection of Ingress
delete collection of Ingress
delete collection of NetworkPolicy
delete collection of NetworkPolicy
delete collection of ReplicaSet
delete collection of ReplicaSet
delete collection of PodSecurityPolicy
delete collection of PodSecurityPolicy
delete a DaemonSet
delete a DaemonSet
delete a Deployment
delete a Deployment
delete an Ingress
delete an Ingress
delete a NetworkPolicy
delete a NetworkPolicy
delete a ReplicaSet
delete a ReplicaSet
delete a PodSecurityPolicy
delete a PodSecurityPolicy
get available resources
get available resources
list or watch objects of kind DaemonSet
list or watch objects of kind DaemonSet
list or watch objects of kind Deployment
list or watch objects of kind Deployment
list or watch objects of kind Ingress
list or watch objects of kind Ingress
list or watch objects of kind DaemonSet
list or watch objects of kind DaemonSet
list or watch objects of kind Deployment
list or watch objects of kind Deployment
list or watch objects of kind Ingress
list or watch objects of kind Ingress
list or watch objects of kind NetworkPolicy
list or watch objects of kind NetworkPolicy
list or watch objects of kind ReplicaSet
list or watch objects of kind ReplicaSet
list or watch objects of kind NetworkPolicy
list or watch objects of kind NetworkPolicy
list or watch objects of kind PodSecurityPolicy
list or watch objects of kind PodSecurityPolicy
list or watch objects of kind ReplicaSet
list or watch objects of kind ReplicaSet
partially update the specified DaemonSet
partially update the specified DaemonSet
partially update status of the specified DaemonSet
partially update status of the specified DaemonSet
partially update the specified Deployment
partially update the specified Deployment
partially update scale of the specified Deployment
partially update scale of the specified Deployment
partially update status of the specified Deployment
partially update status of the specified Deployment
partially update the specified Ingress
partially update the specified Ingress
partially update status of the specified Ingress
partially update status of the specified Ingress
partially update the specified NetworkPolicy
partially update the specified NetworkPolicy
partially update the specified ReplicaSet
partially update the specified ReplicaSet
partially update scale of the specified ReplicaSet
partially update scale of the specified ReplicaSet
partially update status of the specified ReplicaSet
partially update status of the specified ReplicaSet
partially update scale of the specified ReplicationControllerDummy
partially update scale of the specified ReplicationControllerDummy
partially update the specified PodSecurityPolicy
partially update the specified PodSecurityPolicy
read the specified DaemonSet
read the specified DaemonSet
read status of the specified DaemonSet
read status of the specified DaemonSet
read the specified Deployment
read the specified Deployment
read scale of the specified Deployment
read scale of the specified Deployment
read status of the specified Deployment
read status of the specified Deployment
read the specified Ingress
read the specified Ingress
read status of the specified Ingress
read status of the specified Ingress
read the specified NetworkPolicy
read the specified NetworkPolicy
read the specified ReplicaSet
read the specified ReplicaSet
read scale of the specified ReplicaSet
read scale of the specified ReplicaSet
read status of the specified ReplicaSet
read status of the specified ReplicaSet
read scale of the specified ReplicationControllerDummy
read scale of the specified ReplicationControllerDummy
read the specified PodSecurityPolicy
read the specified PodSecurityPolicy
replace the specified DaemonSet
replace the specified DaemonSet
replace status of the specified DaemonSet
replace status of the specified DaemonSet
replace the specified Deployment
replace the specified Deployment
replace scale of the specified Deployment
replace scale of the specified Deployment
replace status of the specified Deployment
replace status of the specified Deployment
replace the specified Ingress
replace the specified Ingress
replace status of the specified Ingress
replace status of the specified Ingress
replace the specified NetworkPolicy
replace the specified NetworkPolicy
replace the specified ReplicaSet
replace the specified ReplicaSet
replace scale of the specified ReplicaSet
replace scale of the specified ReplicaSet
replace status of the specified ReplicaSet
replace status of the specified ReplicaSet
replace scale of the specified ReplicationControllerDummy
replace scale of the specified ReplicationControllerDummy
replace the specified PodSecurityPolicy
replace the specified PodSecurityPolicy
watch individual changes to a list of DaemonSet
watch individual changes to a list of DaemonSet
watch individual changes to a list of Deployment
watch individual changes to a list of Deployment
watch individual changes to a list of Ingress
watch individual changes to a list of Ingress
watch changes to an object of kind DaemonSet
watch changes to an object of kind DaemonSet
watch individual changes to a list of DaemonSet
watch individual changes to a list of DaemonSet
watch changes to an object of kind Deployment
watch changes to an object of kind Deployment
watch individual changes to a list of Deployment
watch individual changes to a list of Deployment
watch changes to an object of kind Ingress
watch changes to an object of kind Ingress
watch individual changes to a list of Ingress
watch individual changes to a list of Ingress
watch changes to an object of kind NetworkPolicy
watch changes to an object of kind NetworkPolicy
watch individual changes to a list of NetworkPolicy
watch individual changes to a list of NetworkPolicy
watch changes to an object of kind ReplicaSet
watch changes to an object of kind ReplicaSet
watch individual changes to a list of ReplicaSet
watch individual changes to a list of ReplicaSet
watch individual changes to a list of NetworkPolicy
watch individual changes to a list of NetworkPolicy
watch changes to an object of kind PodSecurityPolicy
watch changes to an object of kind PodSecurityPolicy
watch individual changes to a list of PodSecurityPolicy
watch individual changes to a list of PodSecurityPolicy
watch individual changes to a list of ReplicaSet
watch individual changes to a list of ReplicaSet
Link to this section Functions
create a DaemonSet
OpenAPI Operation ID: createExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DaemonSet
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a DaemonSet
OpenAPI Operation ID: createExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DaemonSet
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a Deployment
OpenAPI Operation ID: createExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Deployment
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a Deployment
OpenAPI Operation ID: createExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Deployment
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create rollback of a Deployment
OpenAPI Operation ID: createExtensionsV1beta1NamespacedDeploymentRollback
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DeploymentRollback
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DeploymentRollback
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create rollback of a Deployment
OpenAPI Operation ID: createExtensionsV1beta1NamespacedDeploymentRollback
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DeploymentRollback
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DeploymentRollback
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create an Ingress
OpenAPI Operation ID: createExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Ingress
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create an Ingress
OpenAPI Operation ID: createExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Ingress
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a NetworkPolicy
OpenAPI Operation ID: createExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.NetworkPolicy
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a NetworkPolicy
OpenAPI Operation ID: createExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.NetworkPolicy
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a ReplicaSet
OpenAPI Operation ID: createExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.ReplicaSet
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a ReplicaSet
OpenAPI Operation ID: createExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.ReplicaSet
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a PodSecurityPolicy
OpenAPI Operation ID: createExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.PodSecurityPolicy
.
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a PodSecurityPolicy
OpenAPI Operation ID: createExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.PodSecurityPolicy
.
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
delete collection of DaemonSet
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of DaemonSet
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of Deployment
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of Deployment
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of Ingress
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of Ingress
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of NetworkPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of NetworkPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of ReplicaSet
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of ReplicaSet
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionNamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of PodSecurityPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionPodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of PodSecurityPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1CollectionPodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete a DaemonSet
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a DaemonSet
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a Deployment
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a Deployment
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete an Ingress
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete an Ingress
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a NetworkPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a NetworkPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a ReplicaSet
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a ReplicaSet
OpenAPI Operation ID: deleteExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a PodSecurityPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a PodSecurityPolicy
OpenAPI Operation ID: deleteExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
list or watch objects of kind DaemonSet
OpenAPI Operation ID: listExtensionsV1beta1DaemonSetForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind DaemonSet
OpenAPI Operation ID: listExtensionsV1beta1DaemonSetForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Deployment
OpenAPI Operation ID: listExtensionsV1beta1DeploymentForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Deployment
OpenAPI Operation ID: listExtensionsV1beta1DeploymentForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Ingress
OpenAPI Operation ID: listExtensionsV1beta1IngressForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Ingress
OpenAPI Operation ID: listExtensionsV1beta1IngressForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind DaemonSet
OpenAPI Operation ID: listExtensionsV1beta1NamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind DaemonSet
OpenAPI Operation ID: listExtensionsV1beta1NamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Deployment
OpenAPI Operation ID: listExtensionsV1beta1NamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Deployment
OpenAPI Operation ID: listExtensionsV1beta1NamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Ingress
OpenAPI Operation ID: listExtensionsV1beta1NamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind Ingress
OpenAPI Operation ID: listExtensionsV1beta1NamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind NetworkPolicy
OpenAPI Operation ID: listExtensionsV1beta1NamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind NetworkPolicy
OpenAPI Operation ID: listExtensionsV1beta1NamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind ReplicaSet
OpenAPI Operation ID: listExtensionsV1beta1NamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind ReplicaSet
OpenAPI Operation ID: listExtensionsV1beta1NamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind NetworkPolicy
OpenAPI Operation ID: listExtensionsV1beta1NetworkPolicyForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind NetworkPolicy
OpenAPI Operation ID: listExtensionsV1beta1NetworkPolicyForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind PodSecurityPolicy
OpenAPI Operation ID: listExtensionsV1beta1PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind PodSecurityPolicy
OpenAPI Operation ID: listExtensionsV1beta1PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind ReplicaSet
OpenAPI Operation ID: listExtensionsV1beta1ReplicaSetForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
list or watch objects of kind ReplicaSet
OpenAPI Operation ID: listExtensionsV1beta1ReplicaSetForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
partially update the specified DaemonSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified DaemonSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified DaemonSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDaemonSetStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified DaemonSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDaemonSetStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified Deployment
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified Deployment
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update scale of the specified Deployment
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDeploymentScale
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update scale of the specified Deployment
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDeploymentScale
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified Deployment
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDeploymentStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified Deployment
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedDeploymentStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified Ingress
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified Ingress
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified Ingress
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedIngressStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified Ingress
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedIngressStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified NetworkPolicy
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified NetworkPolicy
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified ReplicaSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified ReplicaSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update scale of the specified ReplicaSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicaSetScale
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update scale of the specified ReplicaSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicaSetScale
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified ReplicaSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicaSetStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update status of the specified ReplicaSet
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicaSetStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update scale of the specified ReplicationControllerDummy
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicationControllerDummyScale
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update scale of the specified ReplicationControllerDummy
OpenAPI Operation ID: patchExtensionsV1beta1NamespacedReplicationControllerDummyScale
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified PodSecurityPolicy
OpenAPI Operation ID: patchExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified PodSecurityPolicy
OpenAPI Operation ID: patchExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified DaemonSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read the specified DaemonSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read status of the specified DaemonSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDaemonSetStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read status of the specified DaemonSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDaemonSetStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified Deployment
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read the specified Deployment
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read scale of the specified Deployment
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDeploymentScale
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read scale of the specified Deployment
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDeploymentScale
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read status of the specified Deployment
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDeploymentStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read status of the specified Deployment
OpenAPI Operation ID: readExtensionsV1beta1NamespacedDeploymentStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified Ingress
OpenAPI Operation ID: readExtensionsV1beta1NamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read the specified Ingress
OpenAPI Operation ID: readExtensionsV1beta1NamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read status of the specified Ingress
OpenAPI Operation ID: readExtensionsV1beta1NamespacedIngressStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read status of the specified Ingress
OpenAPI Operation ID: readExtensionsV1beta1NamespacedIngressStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified NetworkPolicy
OpenAPI Operation ID: readExtensionsV1beta1NamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read the specified NetworkPolicy
OpenAPI Operation ID: readExtensionsV1beta1NamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read the specified ReplicaSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read the specified ReplicaSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read scale of the specified ReplicaSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicaSetScale
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read scale of the specified ReplicaSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicaSetScale
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read status of the specified ReplicaSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicaSetStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read status of the specified ReplicaSet
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicaSetStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read scale of the specified ReplicationControllerDummy
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicationControllerDummyScale
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read scale of the specified ReplicationControllerDummy
OpenAPI Operation ID: readExtensionsV1beta1NamespacedReplicationControllerDummyScale
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified PodSecurityPolicy
OpenAPI Operation ID: readExtensionsV1beta1PodSecurityPolicy
Parameters
name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
read the specified PodSecurityPolicy
OpenAPI Operation ID: readExtensionsV1beta1PodSecurityPolicy
Parameters
name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.exact
- Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.export
- Should this value be exported. Export strips fields that a user can not specify.
Response
replace the specified DaemonSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DaemonSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified DaemonSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDaemonSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DaemonSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified DaemonSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDaemonSetStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DaemonSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified DaemonSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDaemonSetStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.DaemonSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified Deployment
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Deployment
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified Deployment
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Deployment
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace scale of the specified Deployment
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDeploymentScale
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Scale
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace scale of the specified Deployment
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDeploymentScale
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Scale
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified Deployment
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDeploymentStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Deployment
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified Deployment
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedDeploymentStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Deployment
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified Ingress
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Ingress
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified Ingress
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedIngress
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Ingress
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified Ingress
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedIngressStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Ingress
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified Ingress
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedIngressStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Ingress
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified NetworkPolicy
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.NetworkPolicy
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified NetworkPolicy
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedNetworkPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.NetworkPolicy
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified ReplicaSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.ReplicaSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified ReplicaSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicaSet
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.ReplicaSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace scale of the specified ReplicaSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicaSetScale
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Scale
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace scale of the specified ReplicaSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicaSetScale
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Scale
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified ReplicaSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicaSetStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.ReplicaSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace status of the specified ReplicaSet
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicaSetStatus
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.ReplicaSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace scale of the specified ReplicationControllerDummy
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicationControllerDummyScale
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Scale
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace scale of the specified ReplicationControllerDummy
OpenAPI Operation ID: replaceExtensionsV1beta1NamespacedReplicationControllerDummyScale
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.Scale
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Scale
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified PodSecurityPolicy
OpenAPI Operation ID: replaceExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.PodSecurityPolicy
.name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified PodSecurityPolicy
OpenAPI Operation ID: replaceExtensionsV1beta1PodSecurityPolicy
Parameters
body
- SeeKazan.Apis.Extensions.V1beta1.PodSecurityPolicy
.name
- name of the PodSecurityPolicy
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
watch individual changes to a list of DaemonSet
OpenAPI Operation ID: watchExtensionsV1beta1DaemonSetListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of DaemonSet
OpenAPI Operation ID: watchExtensionsV1beta1DaemonSetListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Deployment
OpenAPI Operation ID: watchExtensionsV1beta1DeploymentListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Deployment
OpenAPI Operation ID: watchExtensionsV1beta1DeploymentListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Ingress
OpenAPI Operation ID: watchExtensionsV1beta1IngressListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Ingress
OpenAPI Operation ID: watchExtensionsV1beta1IngressListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind DaemonSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind DaemonSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDaemonSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the DaemonSet
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of DaemonSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDaemonSetList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of DaemonSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDaemonSetList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind Deployment
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind Deployment
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDeployment
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Deployment
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Deployment
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDeploymentList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Deployment
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedDeploymentList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind Ingress
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind Ingress
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedIngress
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Ingress
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Ingress
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedIngressList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of Ingress
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedIngressList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind NetworkPolicy
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind NetworkPolicy
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedNetworkPolicy
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the NetworkPolicy
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of NetworkPolicy
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedNetworkPolicyList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of NetworkPolicy
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedNetworkPolicyList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind ReplicaSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind ReplicaSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedReplicaSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ReplicaSet
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of ReplicaSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedReplicaSetList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of ReplicaSet
OpenAPI Operation ID: watchExtensionsV1beta1NamespacedReplicaSetList
Parameters
namespace
- object name and auth scope, such as for teams and projects
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of NetworkPolicy
OpenAPI Operation ID: watchExtensionsV1beta1NetworkPolicyListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of NetworkPolicy
OpenAPI Operation ID: watchExtensionsV1beta1NetworkPolicyListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind PodSecurityPolicy
OpenAPI Operation ID: watchExtensionsV1beta1PodSecurityPolicy
Parameters
name
- name of the PodSecurityPolicy
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind PodSecurityPolicy
OpenAPI Operation ID: watchExtensionsV1beta1PodSecurityPolicy
Parameters
name
- name of the PodSecurityPolicy
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of PodSecurityPolicy
OpenAPI Operation ID: watchExtensionsV1beta1PodSecurityPolicyList
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of PodSecurityPolicy
OpenAPI Operation ID: watchExtensionsV1beta1PodSecurityPolicyList
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of ReplicaSet
OpenAPI Operation ID: watchExtensionsV1beta1ReplicaSetListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch individual changes to a list of ReplicaSet
OpenAPI Operation ID: watchExtensionsV1beta1ReplicaSetListForAllNamespaces
Options
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.field_selector
- A selector to restrict the list of returned objects by their fields. Defaults to everything.include_uninitialized
- If true, partially initialized resources are included in the response.label_selector
- A selector to restrict the list of returned objects by their labels. Defaults to everything.limit
- limit is a maximum number of responses to return for a list call. If more items exist, the server will set thecontinue
field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.
The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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
- If ‘true’, then the output is pretty printed.resource_version
- 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.timeout_seconds
- Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.