Kazan v0.7.0 Kazan.Apis.Rbacauthorization.V1 View Source

Contains functions for V1 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

delete collection of ClusterRole

delete collection of ClusterRole

delete collection of ClusterRoleBinding

delete collection of ClusterRoleBinding

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 RoleBinding

read the specified ClusterRole

read the specified ClusterRole

read the specified ClusterRoleBinding

read the specified ClusterRoleBinding

replace the specified ClusterRole

replace the specified ClusterRole

replace the specified ClusterRoleBinding

replace the specified ClusterRoleBinding

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

Link to this function create_cluster_role(body, options \\ []) View Source

create a ClusterRole

OpenAPI Operation ID: createRbacAuthorizationV1ClusterRole

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function create_cluster_role!(body, options \\ []) View Source

create a ClusterRole

OpenAPI Operation ID: createRbacAuthorizationV1ClusterRole

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function create_cluster_role_binding(body, options \\ []) View Source

create a ClusterRoleBinding

OpenAPI Operation ID: createRbacAuthorizationV1ClusterRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function create_cluster_role_binding!(body, options \\ []) View Source

create a ClusterRoleBinding

OpenAPI Operation ID: createRbacAuthorizationV1ClusterRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function create_namespaced_role(body, namespace, options \\ []) View Source

create a Role

OpenAPI Operation ID: createRbacAuthorizationV1NamespacedRole

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function create_namespaced_role!(body, namespace, options \\ []) View Source

create a Role

OpenAPI Operation ID: createRbacAuthorizationV1NamespacedRole

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function create_namespaced_role_binding(body, namespace, options \\ []) View Source

create a RoleBinding

OpenAPI Operation ID: createRbacAuthorizationV1NamespacedRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function create_namespaced_role_binding!(body, namespace, options \\ []) View Source

create a RoleBinding

OpenAPI Operation ID: createRbacAuthorizationV1NamespacedRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function delete_cluster_role(body, name, options \\ []) View Source

delete a ClusterRole

OpenAPI Operation ID: deleteRbacAuthorizationV1ClusterRole

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_cluster_role!(body, name, options \\ []) View Source

delete a ClusterRole

OpenAPI Operation ID: deleteRbacAuthorizationV1ClusterRole

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_cluster_role_binding(body, name, options \\ []) View Source

delete a ClusterRoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1ClusterRoleBinding

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_cluster_role_binding!(body, name, options \\ []) View Source

delete a ClusterRoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1ClusterRoleBinding

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_cluster_role(options \\ []) View Source

delete collection of ClusterRole

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionClusterRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_cluster_role!(options \\ []) View Source

delete collection of ClusterRole

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionClusterRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_cluster_role_binding(options \\ []) View Source

delete collection of ClusterRoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionClusterRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_cluster_role_binding!(options \\ []) View Source

delete collection of ClusterRoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionClusterRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_namespaced_role(namespace, options \\ []) View Source

delete collection of Role

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionNamespacedRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_namespaced_role!(namespace, options \\ []) View Source

delete collection of Role

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionNamespacedRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_namespaced_role_binding(namespace, options \\ []) View Source

delete collection of RoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionNamespacedRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_collection_namespaced_role_binding!(namespace, options \\ []) View Source

delete collection of RoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1CollectionNamespacedRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_namespaced_role(body, namespace, name, options \\ []) View Source

delete a Role

OpenAPI Operation ID: deleteRbacAuthorizationV1NamespacedRole

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_namespaced_role!(body, namespace, name, options \\ []) View Source

delete a Role

OpenAPI Operation ID: deleteRbacAuthorizationV1NamespacedRole

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_namespaced_role_binding(body, namespace, name, options \\ []) View Source

delete a RoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1NamespacedRoleBinding

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

Link to this function delete_namespaced_role_binding!(body, namespace, name, options \\ []) View Source

delete a RoleBinding

OpenAPI Operation ID: deleteRbacAuthorizationV1NamespacedRoleBinding

Parameters

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

See Kazan.Models.Apimachinery.Meta.V1.Status

get available resources

OpenAPI Operation ID: getRbacAuthorizationV1APIResources

Response

See Kazan.Models.Apimachinery.Meta.V1.APIResourceList

get available resources

OpenAPI Operation ID: getRbacAuthorizationV1APIResources

Response

See Kazan.Models.Apimachinery.Meta.V1.APIResourceList

Link to this function list_cluster_role(options \\ []) View Source

list or watch objects of kind ClusterRole

OpenAPI Operation ID: listRbacAuthorizationV1ClusterRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.ClusterRoleList

Link to this function list_cluster_role!(options \\ []) View Source

list or watch objects of kind ClusterRole

OpenAPI Operation ID: listRbacAuthorizationV1ClusterRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.ClusterRoleList

Link to this function list_cluster_role_binding(options \\ []) View Source

list or watch objects of kind ClusterRoleBinding

OpenAPI Operation ID: listRbacAuthorizationV1ClusterRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.ClusterRoleBindingList

Link to this function list_cluster_role_binding!(options \\ []) View Source

list or watch objects of kind ClusterRoleBinding

OpenAPI Operation ID: listRbacAuthorizationV1ClusterRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.ClusterRoleBindingList

Link to this function list_namespaced_role(namespace, options \\ []) View Source

list or watch objects of kind Role

OpenAPI Operation ID: listRbacAuthorizationV1NamespacedRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleList

Link to this function list_namespaced_role!(namespace, options \\ []) View Source

list or watch objects of kind Role

OpenAPI Operation ID: listRbacAuthorizationV1NamespacedRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleList

Link to this function list_namespaced_role_binding(namespace, options \\ []) View Source

list or watch objects of kind RoleBinding

OpenAPI Operation ID: listRbacAuthorizationV1NamespacedRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleBindingList

Link to this function list_namespaced_role_binding!(namespace, options \\ []) View Source

list or watch objects of kind RoleBinding

OpenAPI Operation ID: listRbacAuthorizationV1NamespacedRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleBindingList

Link to this function list_role_binding_for_all_namespaces(options \\ []) View Source

list or watch objects of kind RoleBinding

OpenAPI Operation ID: listRbacAuthorizationV1RoleBindingForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleBindingList

Link to this function list_role_binding_for_all_namespaces!(options \\ []) View Source

list or watch objects of kind RoleBinding

OpenAPI Operation ID: listRbacAuthorizationV1RoleBindingForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleBindingList

Link to this function list_role_for_all_namespaces(options \\ []) View Source

list or watch objects of kind Role

OpenAPI Operation ID: listRbacAuthorizationV1RoleForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleList

Link to this function list_role_for_all_namespaces!(options \\ []) View Source

list or watch objects of kind Role

OpenAPI Operation ID: listRbacAuthorizationV1RoleForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Apis.Rbac.V1.RoleList

Link to this function patch_cluster_role(body, name, options \\ []) View Source

partially update the specified ClusterRole

OpenAPI Operation ID: patchRbacAuthorizationV1ClusterRole

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • name - name of the ClusterRole

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function patch_cluster_role!(body, name, options \\ []) View Source

partially update the specified ClusterRole

OpenAPI Operation ID: patchRbacAuthorizationV1ClusterRole

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • name - name of the ClusterRole

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function patch_cluster_role_binding(body, name, options \\ []) View Source

partially update the specified ClusterRoleBinding

OpenAPI Operation ID: patchRbacAuthorizationV1ClusterRoleBinding

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • name - name of the ClusterRoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function patch_cluster_role_binding!(body, name, options \\ []) View Source

partially update the specified ClusterRoleBinding

OpenAPI Operation ID: patchRbacAuthorizationV1ClusterRoleBinding

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • name - name of the ClusterRoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function patch_namespaced_role(body, namespace, name, options \\ []) View Source

partially update the specified Role

OpenAPI Operation ID: patchRbacAuthorizationV1NamespacedRole

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the Role

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function patch_namespaced_role!(body, namespace, name, options \\ []) View Source

partially update the specified Role

OpenAPI Operation ID: patchRbacAuthorizationV1NamespacedRole

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the Role

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function patch_namespaced_role_binding(body, namespace, name, options \\ []) View Source

partially update the specified RoleBinding

OpenAPI Operation ID: patchRbacAuthorizationV1NamespacedRoleBinding

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the RoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function patch_namespaced_role_binding!(body, namespace, name, options \\ []) View Source

partially update the specified RoleBinding

OpenAPI Operation ID: patchRbacAuthorizationV1NamespacedRoleBinding

Parameters

  • body - See Kazan.Models.Apimachinery.Meta.V1.Patch.
  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the RoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function read_cluster_role(name, options \\ []) View Source

read the specified ClusterRole

OpenAPI Operation ID: readRbacAuthorizationV1ClusterRole

Parameters

  • name - name of the ClusterRole

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function read_cluster_role!(name, options \\ []) View Source

read the specified ClusterRole

OpenAPI Operation ID: readRbacAuthorizationV1ClusterRole

Parameters

  • name - name of the ClusterRole

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function read_cluster_role_binding(name, options \\ []) View Source

read the specified ClusterRoleBinding

OpenAPI Operation ID: readRbacAuthorizationV1ClusterRoleBinding

Parameters

  • name - name of the ClusterRoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function read_cluster_role_binding!(name, options \\ []) View Source

read the specified ClusterRoleBinding

OpenAPI Operation ID: readRbacAuthorizationV1ClusterRoleBinding

Parameters

  • name - name of the ClusterRoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function read_namespaced_role(namespace, name, options \\ []) View Source

read the specified Role

OpenAPI Operation ID: readRbacAuthorizationV1NamespacedRole

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the Role

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function read_namespaced_role!(namespace, name, options \\ []) View Source

read the specified Role

OpenAPI Operation ID: readRbacAuthorizationV1NamespacedRole

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the Role

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function read_namespaced_role_binding(namespace, name, options \\ []) View Source

read the specified RoleBinding

OpenAPI Operation ID: readRbacAuthorizationV1NamespacedRoleBinding

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the RoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function read_namespaced_role_binding!(namespace, name, options \\ []) View Source

read the specified RoleBinding

OpenAPI Operation ID: readRbacAuthorizationV1NamespacedRoleBinding

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the RoleBinding

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function replace_cluster_role(body, name, options \\ []) View Source

replace the specified ClusterRole

OpenAPI Operation ID: replaceRbacAuthorizationV1ClusterRole

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function replace_cluster_role!(body, name, options \\ []) View Source

replace the specified ClusterRole

OpenAPI Operation ID: replaceRbacAuthorizationV1ClusterRole

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRole

Link to this function replace_cluster_role_binding(body, name, options \\ []) View Source

replace the specified ClusterRoleBinding

OpenAPI Operation ID: replaceRbacAuthorizationV1ClusterRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function replace_cluster_role_binding!(body, name, options \\ []) View Source

replace the specified ClusterRoleBinding

OpenAPI Operation ID: replaceRbacAuthorizationV1ClusterRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.ClusterRoleBinding

Link to this function replace_namespaced_role(body, namespace, name, options \\ []) View Source

replace the specified Role

OpenAPI Operation ID: replaceRbacAuthorizationV1NamespacedRole

Parameters

  • body - See Kazan.Apis.Rbac.V1.Role.
  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the Role

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function replace_namespaced_role!(body, namespace, name, options \\ []) View Source

replace the specified Role

OpenAPI Operation ID: replaceRbacAuthorizationV1NamespacedRole

Parameters

  • body - See Kazan.Apis.Rbac.V1.Role.
  • namespace - object name and auth scope, such as for teams and projects
  • name - name of the Role

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.Role

Link to this function replace_namespaced_role_binding(body, namespace, name, options \\ []) View Source

replace the specified RoleBinding

OpenAPI Operation ID: replaceRbacAuthorizationV1NamespacedRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function replace_namespaced_role_binding!(body, namespace, name, options \\ []) View Source

replace the specified RoleBinding

OpenAPI Operation ID: replaceRbacAuthorizationV1NamespacedRoleBinding

Parameters

Options

  • pretty - If ‘true’, then the output is pretty printed.

Response

See Kazan.Apis.Rbac.V1.RoleBinding

Link to this function watch_cluster_role(name, options \\ []) View Source

watch changes to an object of kind ClusterRole

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_cluster_role!(name, options \\ []) View Source

watch changes to an object of kind ClusterRole

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRole

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_cluster_role_binding(name, options \\ []) View Source

watch changes to an object of kind ClusterRoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_cluster_role_binding!(name, options \\ []) View Source

watch changes to an object of kind ClusterRoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRoleBinding

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_cluster_role_binding_list(options \\ []) View Source

watch individual changes to a list of ClusterRoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRoleBindingList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_cluster_role_binding_list!(options \\ []) View Source

watch individual changes to a list of ClusterRoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRoleBindingList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_cluster_role_list(options \\ []) View Source

watch individual changes to a list of ClusterRole

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRoleList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_cluster_role_list!(options \\ []) View Source

watch individual changes to a list of ClusterRole

OpenAPI Operation ID: watchRbacAuthorizationV1ClusterRoleList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role(namespace, name, options \\ []) View Source

watch changes to an object of kind Role

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRole

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - 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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role!(namespace, name, options \\ []) View Source

watch changes to an object of kind Role

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRole

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - 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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role_binding(namespace, name, options \\ []) View Source

watch changes to an object of kind RoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRoleBinding

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - 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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role_binding!(namespace, name, options \\ []) View Source

watch changes to an object of kind RoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRoleBinding

Parameters

  • namespace - object name and auth scope, such as for teams and projects
  • name - 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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role_binding_list(namespace, options \\ []) View Source

watch individual changes to a list of RoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRoleBindingList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role_binding_list!(namespace, options \\ []) View Source

watch individual changes to a list of RoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRoleBindingList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role_list(namespace, options \\ []) View Source

watch individual changes to a list of Role

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRoleList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_namespaced_role_list!(namespace, options \\ []) View Source

watch individual changes to a list of Role

OpenAPI Operation ID: watchRbacAuthorizationV1NamespacedRoleList

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_role_binding_list_for_all_namespaces(options \\ []) View Source

watch individual changes to a list of RoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1RoleBindingListForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_role_binding_list_for_all_namespaces!(options \\ []) View Source

watch individual changes to a list of RoleBinding

OpenAPI Operation ID: watchRbacAuthorizationV1RoleBindingListForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_role_list_for_all_namespaces(options \\ []) View Source

watch individual changes to a list of Role

OpenAPI Operation ID: watchRbacAuthorizationV1RoleListForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent

Link to this function watch_role_list_for_all_namespaces!(options \\ []) View Source

watch individual changes to a list of Role

OpenAPI Operation ID: watchRbacAuthorizationV1RoleListForAllNamespaces

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 the continue field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.

The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are 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

See Kazan.Models.Apimachinery.Meta.V1.WatchEvent