Kazan v0.10.0 Kazan.Apis.Apps.V1beta1 View Source
Contains functions for V1beta1 of the Apps 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 Apps API.
Link to this section Summary
Functions
create a ControllerRevision
create a ControllerRevision
create a Deployment
create a Deployment
create rollback of a Deployment
create rollback of a Deployment
create a StatefulSet
create a StatefulSet
delete collection of ControllerRevision
delete collection of ControllerRevision
delete collection of Deployment
delete collection of Deployment
delete collection of StatefulSet
delete collection of StatefulSet
delete a ControllerRevision
delete a ControllerRevision
delete a Deployment
delete a Deployment
delete a StatefulSet
delete a StatefulSet
get available resources
get available resources
list or watch objects of kind ControllerRevision
list or watch objects of kind ControllerRevision
list or watch objects of kind Deployment
list or watch objects of kind Deployment
list or watch objects of kind ControllerRevision
list or watch objects of kind ControllerRevision
list or watch objects of kind Deployment
list or watch objects of kind Deployment
list or watch objects of kind StatefulSet
list or watch objects of kind StatefulSet
list or watch objects of kind StatefulSet
list or watch objects of kind StatefulSet
partially update the specified ControllerRevision
partially update the specified ControllerRevision
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 StatefulSet
partially update the specified StatefulSet
partially update scale of the specified StatefulSet
partially update scale of the specified StatefulSet
partially update status of the specified StatefulSet
partially update status of the specified StatefulSet
read the specified ControllerRevision
read the specified ControllerRevision
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 StatefulSet
read the specified StatefulSet
read scale of the specified StatefulSet
read scale of the specified StatefulSet
read status of the specified StatefulSet
read status of the specified StatefulSet
replace the specified ControllerRevision
replace the specified ControllerRevision
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 StatefulSet
replace the specified StatefulSet
replace scale of the specified StatefulSet
replace scale of the specified StatefulSet
replace status of the specified StatefulSet
replace status of the specified StatefulSet
watch individual changes to a list of ControllerRevision
watch individual changes to a list of ControllerRevision
watch individual changes to a list of Deployment
watch individual changes to a list of Deployment
watch changes to an object of kind ControllerRevision
watch changes to an object of kind ControllerRevision
watch individual changes to a list of ControllerRevision
watch individual changes to a list of ControllerRevision
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 StatefulSet
watch changes to an object of kind StatefulSet
watch individual changes to a list of StatefulSet
watch individual changes to a list of StatefulSet
watch individual changes to a list of StatefulSet
watch individual changes to a list of StatefulSet
Link to this section Functions
create_namespaced_controller_revision!( Kazan.Apis.Apps.V1beta1.ControllerRevision.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
create a ControllerRevision
OpenAPI Operation ID: createAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.ControllerRevision
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create_namespaced_controller_revision( Kazan.Apis.Apps.V1beta1.ControllerRevision.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
create a ControllerRevision
OpenAPI Operation ID: createAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.ControllerRevision
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create_namespaced_deployment!( Kazan.Apis.Apps.V1beta1.Deployment.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
create a Deployment
OpenAPI Operation ID: createAppsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment( Kazan.Apis.Apps.V1beta1.Deployment.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
create a Deployment
OpenAPI Operation ID: createAppsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment_rollback!( Kazan.Apis.Apps.V1beta1.DeploymentRollback.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
create rollback of a Deployment
OpenAPI Operation ID: createAppsV1beta1NamespacedDeploymentRollback
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment_rollback( Kazan.Apis.Apps.V1beta1.DeploymentRollback.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
create rollback of a Deployment
OpenAPI Operation ID: createAppsV1beta1NamespacedDeploymentRollback
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_stateful_set!( Kazan.Apis.Apps.V1beta1.StatefulSet.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
create a StatefulSet
OpenAPI Operation ID: createAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.StatefulSet
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create_namespaced_stateful_set( Kazan.Apis.Apps.V1beta1.StatefulSet.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
create a StatefulSet
OpenAPI Operation ID: createAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.StatefulSet
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
delete_collection_namespaced_controller_revision!(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: Kazan.Request.t()
delete collection of ControllerRevision
OpenAPI Operation ID: deleteAppsV1beta1CollectionNamespacedControllerRevision
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_namespaced_controller_revision(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
delete collection of ControllerRevision
OpenAPI Operation ID: deleteAppsV1beta1CollectionNamespacedControllerRevision
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_namespaced_deployment!(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: Kazan.Request.t()
delete collection of Deployment
OpenAPI Operation ID: deleteAppsV1beta1CollectionNamespacedDeployment
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_namespaced_deployment(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
delete collection of Deployment
OpenAPI Operation ID: deleteAppsV1beta1CollectionNamespacedDeployment
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_namespaced_stateful_set!(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: Kazan.Request.t()
delete collection of StatefulSet
OpenAPI Operation ID: deleteAppsV1beta1CollectionNamespacedStatefulSet
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_namespaced_stateful_set(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
delete collection of StatefulSet
OpenAPI Operation ID: deleteAppsV1beta1CollectionNamespacedStatefulSet
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_namespaced_controller_revision!( Kazan.Models.Apimachinery.Meta.V1.DeleteOptions.t(), String.t(), String.t(), pretty: String.t(), grace_period_seconds: integer(), orphan_dependents: boolean(), propagation_policy: String.t() ) :: Kazan.Request.t()
delete a ControllerRevision
OpenAPI Operation ID: deleteAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
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_namespaced_controller_revision( Kazan.Models.Apimachinery.Meta.V1.DeleteOptions.t(), String.t(), String.t(), pretty: String.t(), grace_period_seconds: integer(), orphan_dependents: boolean(), propagation_policy: String.t() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
delete a ControllerRevision
OpenAPI Operation ID: deleteAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
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_namespaced_deployment!( Kazan.Models.Apimachinery.Meta.V1.DeleteOptions.t(), String.t(), String.t(), pretty: String.t(), grace_period_seconds: integer(), orphan_dependents: boolean(), propagation_policy: String.t() ) :: Kazan.Request.t()
delete a Deployment
OpenAPI Operation ID: deleteAppsV1beta1NamespacedDeployment
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_namespaced_deployment( Kazan.Models.Apimachinery.Meta.V1.DeleteOptions.t(), String.t(), String.t(), pretty: String.t(), grace_period_seconds: integer(), orphan_dependents: boolean(), propagation_policy: String.t() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
delete a Deployment
OpenAPI Operation ID: deleteAppsV1beta1NamespacedDeployment
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_namespaced_stateful_set!( Kazan.Models.Apimachinery.Meta.V1.DeleteOptions.t(), String.t(), String.t(), pretty: String.t(), grace_period_seconds: integer(), orphan_dependents: boolean(), propagation_policy: String.t() ) :: Kazan.Request.t()
delete a StatefulSet
OpenAPI Operation ID: deleteAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
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_namespaced_stateful_set( Kazan.Models.Apimachinery.Meta.V1.DeleteOptions.t(), String.t(), String.t(), pretty: String.t(), grace_period_seconds: integer(), orphan_dependents: boolean(), propagation_policy: String.t() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
delete a StatefulSet
OpenAPI Operation ID: deleteAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
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
get_api_resources() :: {:ok, Kazan.Request.t()} | {:error, term()}
get available resources
OpenAPI Operation ID: getAppsV1beta1APIResources
Response
list or watch objects of kind ControllerRevision
OpenAPI Operation ID: listAppsV1beta1ControllerRevisionForAllNamespaces
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_controller_revision_for_all_namespaces( continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
list or watch objects of kind ControllerRevision
OpenAPI Operation ID: listAppsV1beta1ControllerRevisionForAllNamespaces
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: listAppsV1beta1DeploymentForAllNamespaces
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_deployment_for_all_namespaces( continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
list or watch objects of kind Deployment
OpenAPI Operation ID: listAppsV1beta1DeploymentForAllNamespaces
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 ControllerRevision
OpenAPI Operation ID: listAppsV1beta1NamespacedControllerRevision
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_namespaced_controller_revision(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
list or watch objects of kind ControllerRevision
OpenAPI Operation ID: listAppsV1beta1NamespacedControllerRevision
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: listAppsV1beta1NamespacedDeployment
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_namespaced_deployment(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
list or watch objects of kind Deployment
OpenAPI Operation ID: listAppsV1beta1NamespacedDeployment
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 StatefulSet
OpenAPI Operation ID: listAppsV1beta1NamespacedStatefulSet
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_namespaced_stateful_set(String.t(), pretty: String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
list or watch objects of kind StatefulSet
OpenAPI Operation ID: listAppsV1beta1NamespacedStatefulSet
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 StatefulSet
OpenAPI Operation ID: listAppsV1beta1StatefulSetForAllNamespaces
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_stateful_set_for_all_namespaces( continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
list or watch objects of kind StatefulSet
OpenAPI Operation ID: listAppsV1beta1StatefulSetForAllNamespaces
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
patch_namespaced_controller_revision!( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
partially update the specified ControllerRevision
OpenAPI Operation ID: patchAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
patch_namespaced_controller_revision( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
partially update the specified ControllerRevision
OpenAPI Operation ID: patchAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
patch_namespaced_deployment!( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
partially update the specified Deployment
OpenAPI Operation ID: patchAppsV1beta1NamespacedDeployment
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
patch_namespaced_deployment( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
partially update the specified Deployment
OpenAPI Operation ID: patchAppsV1beta1NamespacedDeployment
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
patch_namespaced_deployment_scale!( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
partially update scale of the specified Deployment
OpenAPI Operation ID: patchAppsV1beta1NamespacedDeploymentScale
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
patch_namespaced_deployment_scale( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
partially update scale of the specified Deployment
OpenAPI Operation ID: patchAppsV1beta1NamespacedDeploymentScale
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
patch_namespaced_deployment_status!( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
partially update status of the specified Deployment
OpenAPI Operation ID: patchAppsV1beta1NamespacedDeploymentStatus
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
patch_namespaced_deployment_status( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
partially update status of the specified Deployment
OpenAPI Operation ID: patchAppsV1beta1NamespacedDeploymentStatus
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
patch_namespaced_stateful_set!( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
partially update the specified StatefulSet
OpenAPI Operation ID: patchAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
patch_namespaced_stateful_set( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
partially update the specified StatefulSet
OpenAPI Operation ID: patchAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
patch_namespaced_stateful_set_scale!( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
partially update scale of the specified StatefulSet
OpenAPI Operation ID: patchAppsV1beta1NamespacedStatefulSetScale
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
patch_namespaced_stateful_set_scale( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
partially update scale of the specified StatefulSet
OpenAPI Operation ID: patchAppsV1beta1NamespacedStatefulSetScale
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
patch_namespaced_stateful_set_status!( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
partially update status of the specified StatefulSet
OpenAPI Operation ID: patchAppsV1beta1NamespacedStatefulSetStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
patch_namespaced_stateful_set_status( Kazan.Models.Apimachinery.Meta.V1.Patch.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
partially update status of the specified StatefulSet
OpenAPI Operation ID: patchAppsV1beta1NamespacedStatefulSetStatus
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified ControllerRevision
OpenAPI Operation ID: readAppsV1beta1NamespacedControllerRevision
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
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 ControllerRevision
OpenAPI Operation ID: readAppsV1beta1NamespacedControllerRevision
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
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: readAppsV1beta1NamespacedDeployment
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: readAppsV1beta1NamespacedDeployment
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_namespaced_deployment_scale!(String.t(), String.t(), [ {:pretty, String.t()} ]) :: Kazan.Request.t()
read scale of the specified Deployment
OpenAPI Operation ID: readAppsV1beta1NamespacedDeploymentScale
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_namespaced_deployment_scale(String.t(), String.t(), [{:pretty, String.t()}]) :: {:ok, Kazan.Request.t()} | {:error, term()}
read scale of the specified Deployment
OpenAPI Operation ID: readAppsV1beta1NamespacedDeploymentScale
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_namespaced_deployment_status!(String.t(), String.t(), [ {:pretty, String.t()} ]) :: Kazan.Request.t()
read status of the specified Deployment
OpenAPI Operation ID: readAppsV1beta1NamespacedDeploymentStatus
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_namespaced_deployment_status(String.t(), String.t(), [ {:pretty, String.t()} ]) :: {:ok, Kazan.Request.t()} | {:error, term()}
read status of the specified Deployment
OpenAPI Operation ID: readAppsV1beta1NamespacedDeploymentStatus
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 StatefulSet
OpenAPI Operation ID: readAppsV1beta1NamespacedStatefulSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
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 StatefulSet
OpenAPI Operation ID: readAppsV1beta1NamespacedStatefulSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
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_namespaced_stateful_set_scale!(String.t(), String.t(), [ {:pretty, String.t()} ]) :: Kazan.Request.t()
read scale of the specified StatefulSet
OpenAPI Operation ID: readAppsV1beta1NamespacedStatefulSetScale
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_namespaced_stateful_set_scale(String.t(), String.t(), [ {:pretty, String.t()} ]) :: {:ok, Kazan.Request.t()} | {:error, term()}
read scale of the specified StatefulSet
OpenAPI Operation ID: readAppsV1beta1NamespacedStatefulSetScale
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_namespaced_stateful_set_status!(String.t(), String.t(), [ {:pretty, String.t()} ]) :: Kazan.Request.t()
read status of the specified StatefulSet
OpenAPI Operation ID: readAppsV1beta1NamespacedStatefulSetStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read_namespaced_stateful_set_status(String.t(), String.t(), [ {:pretty, String.t()} ]) :: {:ok, Kazan.Request.t()} | {:error, term()}
read status of the specified StatefulSet
OpenAPI Operation ID: readAppsV1beta1NamespacedStatefulSetStatus
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace_namespaced_controller_revision!( Kazan.Apis.Apps.V1beta1.ControllerRevision.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
replace the specified ControllerRevision
OpenAPI Operation ID: replaceAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.ControllerRevision
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace_namespaced_controller_revision( Kazan.Apis.Apps.V1beta1.ControllerRevision.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
replace the specified ControllerRevision
OpenAPI Operation ID: replaceAppsV1beta1NamespacedControllerRevision
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.ControllerRevision
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace_namespaced_deployment!( Kazan.Apis.Apps.V1beta1.Deployment.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
replace the specified Deployment
OpenAPI Operation ID: replaceAppsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment( Kazan.Apis.Apps.V1beta1.Deployment.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
replace the specified Deployment
OpenAPI Operation ID: replaceAppsV1beta1NamespacedDeployment
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment_scale!( Kazan.Apis.Apps.V1beta1.Scale.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
replace scale of the specified Deployment
OpenAPI Operation ID: replaceAppsV1beta1NamespacedDeploymentScale
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment_scale( Kazan.Apis.Apps.V1beta1.Scale.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
replace scale of the specified Deployment
OpenAPI Operation ID: replaceAppsV1beta1NamespacedDeploymentScale
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment_status!( Kazan.Apis.Apps.V1beta1.Deployment.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
replace status of the specified Deployment
OpenAPI Operation ID: replaceAppsV1beta1NamespacedDeploymentStatus
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_deployment_status( Kazan.Apis.Apps.V1beta1.Deployment.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
replace status of the specified Deployment
OpenAPI Operation ID: replaceAppsV1beta1NamespacedDeploymentStatus
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_stateful_set!( Kazan.Apis.Apps.V1beta1.StatefulSet.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
replace the specified StatefulSet
OpenAPI Operation ID: replaceAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.StatefulSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace_namespaced_stateful_set( Kazan.Apis.Apps.V1beta1.StatefulSet.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
replace the specified StatefulSet
OpenAPI Operation ID: replaceAppsV1beta1NamespacedStatefulSet
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.StatefulSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace_namespaced_stateful_set_scale!( Kazan.Apis.Apps.V1beta1.Scale.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
replace scale of the specified StatefulSet
OpenAPI Operation ID: replaceAppsV1beta1NamespacedStatefulSetScale
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_stateful_set_scale( Kazan.Apis.Apps.V1beta1.Scale.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
replace scale of the specified StatefulSet
OpenAPI Operation ID: replaceAppsV1beta1NamespacedStatefulSetScale
Parameters
body
- SeeKazan.Apis.Apps.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_namespaced_stateful_set_status!( Kazan.Apis.Apps.V1beta1.StatefulSet.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: Kazan.Request.t()
replace status of the specified StatefulSet
OpenAPI Operation ID: replaceAppsV1beta1NamespacedStatefulSetStatus
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.StatefulSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace_namespaced_stateful_set_status( Kazan.Apis.Apps.V1beta1.StatefulSet.t(), String.t(), String.t(), [{:pretty, String.t()}] ) :: {:ok, Kazan.Request.t()} | {:error, term()}
replace status of the specified StatefulSet
OpenAPI Operation ID: replaceAppsV1beta1NamespacedStatefulSetStatus
Parameters
body
- SeeKazan.Apis.Apps.V1beta1.StatefulSet
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
watch individual changes to a list of ControllerRevision
OpenAPI Operation ID: watchAppsV1beta1ControllerRevisionListForAllNamespaces
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_controller_revision_list_for_all_namespaces( continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch individual changes to a list of ControllerRevision
OpenAPI Operation ID: watchAppsV1beta1ControllerRevisionListForAllNamespaces
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: watchAppsV1beta1DeploymentListForAllNamespaces
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_deployment_list_for_all_namespaces( continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch individual changes to a list of Deployment
OpenAPI Operation ID: watchAppsV1beta1DeploymentListForAllNamespaces
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_namespaced_controller_revision!(String.t(), String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: Kazan.Request.t()
watch changes to an object of kind ControllerRevision
OpenAPI Operation ID: watchAppsV1beta1NamespacedControllerRevision
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
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_namespaced_controller_revision(String.t(), String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch changes to an object of kind ControllerRevision
OpenAPI Operation ID: watchAppsV1beta1NamespacedControllerRevision
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the ControllerRevision
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_namespaced_controller_revision_list!(String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: Kazan.Request.t()
watch individual changes to a list of ControllerRevision
OpenAPI Operation ID: watchAppsV1beta1NamespacedControllerRevisionList
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_namespaced_controller_revision_list(String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch individual changes to a list of ControllerRevision
OpenAPI Operation ID: watchAppsV1beta1NamespacedControllerRevisionList
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_namespaced_deployment!(String.t(), String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: Kazan.Request.t()
watch changes to an object of kind Deployment
OpenAPI Operation ID: watchAppsV1beta1NamespacedDeployment
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_namespaced_deployment(String.t(), String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch changes to an object of kind Deployment
OpenAPI Operation ID: watchAppsV1beta1NamespacedDeployment
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: watchAppsV1beta1NamespacedDeploymentList
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_namespaced_deployment_list(String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch individual changes to a list of Deployment
OpenAPI Operation ID: watchAppsV1beta1NamespacedDeploymentList
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_namespaced_stateful_set!(String.t(), String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: Kazan.Request.t()
watch changes to an object of kind StatefulSet
OpenAPI Operation ID: watchAppsV1beta1NamespacedStatefulSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
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_namespaced_stateful_set(String.t(), String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch changes to an object of kind StatefulSet
OpenAPI Operation ID: watchAppsV1beta1NamespacedStatefulSet
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the StatefulSet
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 StatefulSet
OpenAPI Operation ID: watchAppsV1beta1NamespacedStatefulSetList
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_namespaced_stateful_set_list(String.t(), continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch individual changes to a list of StatefulSet
OpenAPI Operation ID: watchAppsV1beta1NamespacedStatefulSetList
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 StatefulSet
OpenAPI Operation ID: watchAppsV1beta1StatefulSetListForAllNamespaces
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_stateful_set_list_for_all_namespaces( continue: String.t(), field_selector: String.t(), include_uninitialized: boolean(), label_selector: String.t(), limit: integer(), pretty: String.t(), resource_version: String.t(), timeout_seconds: integer(), watch: boolean() ) :: {:ok, Kazan.Request.t()} | {:error, term()}
watch individual changes to a list of StatefulSet
OpenAPI Operation ID: watchAppsV1beta1StatefulSetListForAllNamespaces
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.