Kazan v0.7.0 Kazan.Apis.Rbacauthorization.V1alpha1 View Source
Contains functions for V1alpha1 of the Rbacauthorization 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 Rbacauthorization API.
Link to this section Summary
Functions
create a ClusterRole
create a ClusterRole
create a ClusterRoleBinding
create a ClusterRoleBinding
create a Role
create a Role
create a RoleBinding
create a RoleBinding
delete a ClusterRole
delete a ClusterRole
delete a ClusterRoleBinding
delete a ClusterRoleBinding
delete collection of ClusterRole
delete collection of ClusterRole
delete collection of ClusterRoleBinding
delete collection of ClusterRoleBinding
delete collection of Role
delete collection of Role
delete collection of RoleBinding
delete collection of RoleBinding
delete a RoleBinding
delete a RoleBinding
get available resources
get available resources
list or watch objects of kind ClusterRole
list or watch objects of kind ClusterRole
list or watch objects of kind ClusterRoleBinding
list or watch objects of kind ClusterRoleBinding
list or watch objects of kind Role
list or watch objects of kind Role
list or watch objects of kind RoleBinding
list or watch objects of kind RoleBinding
list or watch objects of kind RoleBinding
list or watch objects of kind RoleBinding
list or watch objects of kind Role
list or watch objects of kind Role
partially update the specified ClusterRole
partially update the specified ClusterRole
partially update the specified ClusterRoleBinding
partially update the specified ClusterRoleBinding
partially update the specified Role
partially update the specified Role
partially update the specified RoleBinding
partially update the specified RoleBinding
read the specified ClusterRole
read the specified ClusterRole
read the specified ClusterRoleBinding
read the specified ClusterRoleBinding
read the specified Role
read the specified Role
read the specified RoleBinding
read the specified RoleBinding
replace the specified ClusterRole
replace the specified ClusterRole
replace the specified ClusterRoleBinding
replace the specified ClusterRoleBinding
replace the specified Role
replace the specified Role
replace the specified RoleBinding
replace the specified RoleBinding
watch changes to an object of kind ClusterRole
watch changes to an object of kind ClusterRole
watch changes to an object of kind ClusterRoleBinding
watch changes to an object of kind ClusterRoleBinding
watch individual changes to a list of ClusterRoleBinding
watch individual changes to a list of ClusterRoleBinding
watch individual changes to a list of ClusterRole
watch individual changes to a list of ClusterRole
watch changes to an object of kind Role
watch changes to an object of kind Role
watch changes to an object of kind RoleBinding
watch changes to an object of kind RoleBinding
watch individual changes to a list of RoleBinding
watch individual changes to a list of RoleBinding
watch individual changes to a list of Role
watch individual changes to a list of Role
watch individual changes to a list of RoleBinding
watch individual changes to a list of RoleBinding
watch individual changes to a list of Role
watch individual changes to a list of Role
Link to this section Functions
create a ClusterRole
OpenAPI Operation ID: createRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRole
.
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a ClusterRole
OpenAPI Operation ID: createRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRole
.
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a ClusterRoleBinding
OpenAPI Operation ID: createRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRoleBinding
.
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a ClusterRoleBinding
OpenAPI Operation ID: createRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRoleBinding
.
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a Role
OpenAPI Operation ID: createRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.Role
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a Role
OpenAPI Operation ID: createRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.Role
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a RoleBinding
OpenAPI Operation ID: createRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.RoleBinding
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
create a RoleBinding
OpenAPI Operation ID: createRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.RoleBinding
.namespace
- object name and auth scope, such as for teams and projects
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
delete a ClusterRole
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a ClusterRole
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a ClusterRoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.name
- name of the ClusterRoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a ClusterRoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.name
- name of the ClusterRoleBinding
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 collection of ClusterRole
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionClusterRole
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of ClusterRole
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionClusterRole
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of ClusterRoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionClusterRoleBinding
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of ClusterRoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionClusterRoleBinding
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of Role
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionNamespacedRole
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of Role
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionNamespacedRole
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of RoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionNamespacedRoleBinding
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete collection of RoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1CollectionNamespacedRoleBinding
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
delete a Role
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a Role
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a RoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
delete a RoleBinding
OpenAPI Operation ID: deleteRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.DeleteOptions
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.grace_period_seconds
- The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.orphan_dependents
- Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.propagation_policy
- Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: ‘Orphan’ - orphan the dependents; ‘Background’ - allow the garbage collector to delete the dependents in the background; ‘Foreground’ - a cascading policy that deletes all dependents in the foreground.
Response
list or watch objects of kind ClusterRole
OpenAPI Operation ID: listRbacAuthorizationV1alpha1ClusterRole
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.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 ClusterRole
OpenAPI Operation ID: listRbacAuthorizationV1alpha1ClusterRole
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.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 ClusterRoleBinding
OpenAPI Operation ID: listRbacAuthorizationV1alpha1ClusterRoleBinding
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.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 ClusterRoleBinding
OpenAPI Operation ID: listRbacAuthorizationV1alpha1ClusterRoleBinding
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.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 Role
OpenAPI Operation ID: listRbacAuthorizationV1alpha1NamespacedRole
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.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 Role
OpenAPI Operation ID: listRbacAuthorizationV1alpha1NamespacedRole
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.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 RoleBinding
OpenAPI Operation ID: listRbacAuthorizationV1alpha1NamespacedRoleBinding
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.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 RoleBinding
OpenAPI Operation ID: listRbacAuthorizationV1alpha1NamespacedRoleBinding
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.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 RoleBinding
OpenAPI Operation ID: listRbacAuthorizationV1alpha1RoleBindingForAllNamespaces
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.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 RoleBinding
OpenAPI Operation ID: listRbacAuthorizationV1alpha1RoleBindingForAllNamespaces
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.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 Role
OpenAPI Operation ID: listRbacAuthorizationV1alpha1RoleForAllNamespaces
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.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 Role
OpenAPI Operation ID: listRbacAuthorizationV1alpha1RoleForAllNamespaces
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
partially update the specified ClusterRole
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified ClusterRole
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified ClusterRoleBinding
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.name
- name of the ClusterRoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified ClusterRoleBinding
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.name
- name of the ClusterRoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified Role
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified Role
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified RoleBinding
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
partially update the specified RoleBinding
OpenAPI Operation ID: patchRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Models.Apimachinery.Meta.V1.Patch
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified ClusterRole
OpenAPI Operation ID: readRbacAuthorizationV1alpha1ClusterRole
Parameters
name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified ClusterRole
OpenAPI Operation ID: readRbacAuthorizationV1alpha1ClusterRole
Parameters
name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified ClusterRoleBinding
OpenAPI Operation ID: readRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
name
- name of the ClusterRoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified ClusterRoleBinding
OpenAPI Operation ID: readRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
name
- name of the ClusterRoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified Role
OpenAPI Operation ID: readRbacAuthorizationV1alpha1NamespacedRole
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified Role
OpenAPI Operation ID: readRbacAuthorizationV1alpha1NamespacedRole
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified RoleBinding
OpenAPI Operation ID: readRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
read the specified RoleBinding
OpenAPI Operation ID: readRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified ClusterRole
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRole
.name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified ClusterRole
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1ClusterRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRole
.name
- name of the ClusterRole
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified ClusterRoleBinding
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRoleBinding
.name
- name of the ClusterRoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified ClusterRoleBinding
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.ClusterRoleBinding
.name
- name of the ClusterRoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified Role
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.Role
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified Role
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1NamespacedRole
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.Role
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified RoleBinding
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.RoleBinding
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
replace the specified RoleBinding
OpenAPI Operation ID: replaceRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
body
- SeeKazan.Apis.Rbac.V1alpha1.RoleBinding
.namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
Options
pretty
- If ‘true’, then the output is pretty printed.
Response
watch changes to an object of kind ClusterRole
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRole
Parameters
name
- name of the ClusterRole
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind ClusterRole
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRole
Parameters
name
- name of the ClusterRole
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind ClusterRoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
name
- name of the ClusterRoleBinding
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind ClusterRoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRoleBinding
Parameters
name
- name of the ClusterRoleBinding
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.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 ClusterRoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRoleBindingList
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.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 ClusterRoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRoleBindingList
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.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 ClusterRole
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRoleList
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.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 ClusterRole
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1ClusterRoleList
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind Role
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRole
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind Role
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRole
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the Role
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind RoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
Response
watch changes to an object of kind RoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRoleBinding
Parameters
namespace
- object name and auth scope, such as for teams and projectsname
- name of the RoleBinding
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.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 RoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRoleBindingList
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.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 RoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRoleBindingList
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.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 Role
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRoleList
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.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 Role
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1NamespacedRoleList
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.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 RoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1RoleBindingListForAllNamespaces
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.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 RoleBinding
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1RoleBindingListForAllNamespaces
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.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 Role
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1RoleListForAllNamespaces
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.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 Role
OpenAPI Operation ID: watchRbacAuthorizationV1alpha1RoleListForAllNamespaces
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.watch
- Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.