RubyGems - zilla - Versions diffs - 0.2.0 → 0.2.2 - Mend

zilla 0.2.0 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2650) hide show

data/docs/RbacAuthorizationV1Api.md DELETED Viewed

@@ -1,3640 +0,0 @@
-# Zilla::RbacAuthorizationV1Api
-All URIs are relative to *http://localhost*
-| Method | HTTP request | Description |
-| ------ | ------------ | ----------- |
-| [**create_rbac_authorization_v1_cluster_role**](RbacAuthorizationV1Api.md#create_rbac_authorization_v1_cluster_role) | **POST** /apis/rbac.authorization.k8s.io/v1/clusterroles |  |
-| [**create_rbac_authorization_v1_cluster_role_binding**](RbacAuthorizationV1Api.md#create_rbac_authorization_v1_cluster_role_binding) | **POST** /apis/rbac.authorization.k8s.io/v1/clusterrolebindings |  |
-| [**create_rbac_authorization_v1_namespaced_role**](RbacAuthorizationV1Api.md#create_rbac_authorization_v1_namespaced_role) | **POST** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles |  |
-| [**create_rbac_authorization_v1_namespaced_role_binding**](RbacAuthorizationV1Api.md#create_rbac_authorization_v1_namespaced_role_binding) | **POST** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings |  |
-| [**delete_rbac_authorization_v1_cluster_role**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_cluster_role) | **DELETE** /apis/rbac.authorization.k8s.io/v1/clusterroles/{name} |  |
-| [**delete_rbac_authorization_v1_cluster_role_binding**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_cluster_role_binding) | **DELETE** /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name} |  |
-| [**delete_rbac_authorization_v1_collection_cluster_role**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_collection_cluster_role) | **DELETE** /apis/rbac.authorization.k8s.io/v1/clusterroles |  |
-| [**delete_rbac_authorization_v1_collection_cluster_role_binding**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_collection_cluster_role_binding) | **DELETE** /apis/rbac.authorization.k8s.io/v1/clusterrolebindings |  |
-| [**delete_rbac_authorization_v1_collection_namespaced_role**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_collection_namespaced_role) | **DELETE** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles |  |
-| [**delete_rbac_authorization_v1_collection_namespaced_role_binding**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_collection_namespaced_role_binding) | **DELETE** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings |  |
-| [**delete_rbac_authorization_v1_namespaced_role**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_namespaced_role) | **DELETE** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name} |  |
-| [**delete_rbac_authorization_v1_namespaced_role_binding**](RbacAuthorizationV1Api.md#delete_rbac_authorization_v1_namespaced_role_binding) | **DELETE** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name} |  |
-| [**get_rbac_authorization_v1_api_resources**](RbacAuthorizationV1Api.md#get_rbac_authorization_v1_api_resources) | **GET** /apis/rbac.authorization.k8s.io/v1/ |  |
-| [**list_rbac_authorization_v1_cluster_role**](RbacAuthorizationV1Api.md#list_rbac_authorization_v1_cluster_role) | **GET** /apis/rbac.authorization.k8s.io/v1/clusterroles |  |
-| [**list_rbac_authorization_v1_cluster_role_binding**](RbacAuthorizationV1Api.md#list_rbac_authorization_v1_cluster_role_binding) | **GET** /apis/rbac.authorization.k8s.io/v1/clusterrolebindings |  |
-| [**list_rbac_authorization_v1_namespaced_role**](RbacAuthorizationV1Api.md#list_rbac_authorization_v1_namespaced_role) | **GET** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles |  |
-| [**list_rbac_authorization_v1_namespaced_role_binding**](RbacAuthorizationV1Api.md#list_rbac_authorization_v1_namespaced_role_binding) | **GET** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings |  |
-| [**list_rbac_authorization_v1_role_binding_for_all_namespaces**](RbacAuthorizationV1Api.md#list_rbac_authorization_v1_role_binding_for_all_namespaces) | **GET** /apis/rbac.authorization.k8s.io/v1/rolebindings |  |
-| [**list_rbac_authorization_v1_role_for_all_namespaces**](RbacAuthorizationV1Api.md#list_rbac_authorization_v1_role_for_all_namespaces) | **GET** /apis/rbac.authorization.k8s.io/v1/roles |  |
-| [**patch_rbac_authorization_v1_cluster_role**](RbacAuthorizationV1Api.md#patch_rbac_authorization_v1_cluster_role) | **PATCH** /apis/rbac.authorization.k8s.io/v1/clusterroles/{name} |  |
-| [**patch_rbac_authorization_v1_cluster_role_binding**](RbacAuthorizationV1Api.md#patch_rbac_authorization_v1_cluster_role_binding) | **PATCH** /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name} |  |
-| [**patch_rbac_authorization_v1_namespaced_role**](RbacAuthorizationV1Api.md#patch_rbac_authorization_v1_namespaced_role) | **PATCH** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name} |  |
-| [**patch_rbac_authorization_v1_namespaced_role_binding**](RbacAuthorizationV1Api.md#patch_rbac_authorization_v1_namespaced_role_binding) | **PATCH** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name} |  |
-| [**read_rbac_authorization_v1_cluster_role**](RbacAuthorizationV1Api.md#read_rbac_authorization_v1_cluster_role) | **GET** /apis/rbac.authorization.k8s.io/v1/clusterroles/{name} |  |
-| [**read_rbac_authorization_v1_cluster_role_binding**](RbacAuthorizationV1Api.md#read_rbac_authorization_v1_cluster_role_binding) | **GET** /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name} |  |
-| [**read_rbac_authorization_v1_namespaced_role**](RbacAuthorizationV1Api.md#read_rbac_authorization_v1_namespaced_role) | **GET** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name} |  |
-| [**read_rbac_authorization_v1_namespaced_role_binding**](RbacAuthorizationV1Api.md#read_rbac_authorization_v1_namespaced_role_binding) | **GET** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name} |  |
-| [**replace_rbac_authorization_v1_cluster_role**](RbacAuthorizationV1Api.md#replace_rbac_authorization_v1_cluster_role) | **PUT** /apis/rbac.authorization.k8s.io/v1/clusterroles/{name} |  |
-| [**replace_rbac_authorization_v1_cluster_role_binding**](RbacAuthorizationV1Api.md#replace_rbac_authorization_v1_cluster_role_binding) | **PUT** /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name} |  |
-| [**replace_rbac_authorization_v1_namespaced_role**](RbacAuthorizationV1Api.md#replace_rbac_authorization_v1_namespaced_role) | **PUT** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name} |  |
-| [**replace_rbac_authorization_v1_namespaced_role_binding**](RbacAuthorizationV1Api.md#replace_rbac_authorization_v1_namespaced_role_binding) | **PUT** /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name} |  |
-| [**watch_rbac_authorization_v1_cluster_role**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_cluster_role) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/clusterroles/{name} |  |
-| [**watch_rbac_authorization_v1_cluster_role_binding**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_cluster_role_binding) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings/{name} |  |
-| [**watch_rbac_authorization_v1_cluster_role_binding_list**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_cluster_role_binding_list) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings |  |
-| [**watch_rbac_authorization_v1_cluster_role_list**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_cluster_role_list) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/clusterroles |  |
-| [**watch_rbac_authorization_v1_namespaced_role**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_namespaced_role) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles/{name} |  |
-| [**watch_rbac_authorization_v1_namespaced_role_binding**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_namespaced_role_binding) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings/{name} |  |
-| [**watch_rbac_authorization_v1_namespaced_role_binding_list**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_namespaced_role_binding_list) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings |  |
-| [**watch_rbac_authorization_v1_namespaced_role_list**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_namespaced_role_list) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles |  |
-| [**watch_rbac_authorization_v1_role_binding_list_for_all_namespaces**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_role_binding_list_for_all_namespaces) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/rolebindings |  |
-| [**watch_rbac_authorization_v1_role_list_for_all_namespaces**](RbacAuthorizationV1Api.md#watch_rbac_authorization_v1_role_list_for_all_namespaces) | **GET** /apis/rbac.authorization.k8s.io/v1/watch/roles |  |
-## create_rbac_authorization_v1_cluster_role
-> <IoK8sApiRbacV1ClusterRole> create_rbac_authorization_v1_cluster_role(body, opts)
-create a ClusterRole
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-body = Zilla::IoK8sApiRbacV1ClusterRole.new # IoK8sApiRbacV1ClusterRole |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.create_rbac_authorization_v1_cluster_role(body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_cluster_role: #{e}"
-end
-```
-#### Using the create_rbac_authorization_v1_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRole>, Integer, Hash)> create_rbac_authorization_v1_cluster_role_with_http_info(body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.create_rbac_authorization_v1_cluster_role_with_http_info(body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRole>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **body** | [**IoK8sApiRbacV1ClusterRole**](IoK8sApiRbacV1ClusterRole.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRole**](IoK8sApiRbacV1ClusterRole.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## create_rbac_authorization_v1_cluster_role_binding
-> <IoK8sApiRbacV1ClusterRoleBinding> create_rbac_authorization_v1_cluster_role_binding(body, opts)
-create a ClusterRoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-body = Zilla::IoK8sApiRbacV1ClusterRoleBinding.new({role_ref: Zilla::IoK8sApiRbacV1RoleRef.new({api_group: 'api_group_example', kind: 'kind_example', name: 'name_example'})}) # IoK8sApiRbacV1ClusterRoleBinding |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.create_rbac_authorization_v1_cluster_role_binding(body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_cluster_role_binding: #{e}"
-end
-```
-#### Using the create_rbac_authorization_v1_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRoleBinding>, Integer, Hash)> create_rbac_authorization_v1_cluster_role_binding_with_http_info(body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.create_rbac_authorization_v1_cluster_role_binding_with_http_info(body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **body** | [**IoK8sApiRbacV1ClusterRoleBinding**](IoK8sApiRbacV1ClusterRoleBinding.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRoleBinding**](IoK8sApiRbacV1ClusterRoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## create_rbac_authorization_v1_namespaced_role
-> <IoK8sApiRbacV1Role> create_rbac_authorization_v1_namespaced_role(namespace, body, opts)
-create a Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-body = Zilla::IoK8sApiRbacV1Role.new # IoK8sApiRbacV1Role |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.create_rbac_authorization_v1_namespaced_role(namespace, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_namespaced_role: #{e}"
-end
-```
-#### Using the create_rbac_authorization_v1_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1Role>, Integer, Hash)> create_rbac_authorization_v1_namespaced_role_with_http_info(namespace, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.create_rbac_authorization_v1_namespaced_role_with_http_info(namespace, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1Role>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **body** | [**IoK8sApiRbacV1Role**](IoK8sApiRbacV1Role.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1Role**](IoK8sApiRbacV1Role.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## create_rbac_authorization_v1_namespaced_role_binding
-> <IoK8sApiRbacV1RoleBinding> create_rbac_authorization_v1_namespaced_role_binding(namespace, body, opts)
-create a RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-body = Zilla::IoK8sApiRbacV1RoleBinding.new({role_ref: Zilla::IoK8sApiRbacV1RoleRef.new({api_group: 'api_group_example', kind: 'kind_example', name: 'name_example'})}) # IoK8sApiRbacV1RoleBinding |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.create_rbac_authorization_v1_namespaced_role_binding(namespace, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_namespaced_role_binding: #{e}"
-end
-```
-#### Using the create_rbac_authorization_v1_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleBinding>, Integer, Hash)> create_rbac_authorization_v1_namespaced_role_binding_with_http_info(namespace, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.create_rbac_authorization_v1_namespaced_role_binding_with_http_info(namespace, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->create_rbac_authorization_v1_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **body** | [**IoK8sApiRbacV1RoleBinding**](IoK8sApiRbacV1RoleBinding.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleBinding**](IoK8sApiRbacV1RoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_cluster_role
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_cluster_role(name, opts)
-delete a ClusterRole
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRole
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  grace_period_seconds: 56, # Integer | 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: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_cluster_role(name, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_cluster_role: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_cluster_role_with_http_info(name, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_cluster_role_with_http_info(name, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRole |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_cluster_role_binding
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_cluster_role_binding(name, opts)
-delete a ClusterRoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRoleBinding
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  grace_period_seconds: 56, # Integer | 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: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_cluster_role_binding(name, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_cluster_role_binding: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_cluster_role_binding_with_http_info(name, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_cluster_role_binding_with_http_info(name, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRoleBinding |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_collection_cluster_role
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_collection_cluster_role(opts)
-delete collection of ClusterRole
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_selector: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  grace_period_seconds: 56, # Integer | 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.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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.
-  orphan_dependents: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_collection_cluster_role(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_cluster_role: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_collection_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_collection_cluster_role_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_collection_cluster_role_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_collection_cluster_role_binding
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_collection_cluster_role_binding(opts)
-delete collection of ClusterRoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_selector: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  grace_period_seconds: 56, # Integer | 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.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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.
-  orphan_dependents: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_collection_cluster_role_binding(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_cluster_role_binding: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_collection_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_collection_cluster_role_binding_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_collection_cluster_role_binding_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_collection_namespaced_role
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_collection_namespaced_role(namespace, opts)
-delete collection of Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_selector: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  grace_period_seconds: 56, # Integer | 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.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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.
-  orphan_dependents: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_collection_namespaced_role(namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_namespaced_role: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_collection_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_collection_namespaced_role_with_http_info(namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_collection_namespaced_role_with_http_info(namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_collection_namespaced_role_binding
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_collection_namespaced_role_binding(namespace, opts)
-delete collection of RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_selector: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  grace_period_seconds: 56, # Integer | 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.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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.
-  orphan_dependents: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_collection_namespaced_role_binding(namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_namespaced_role_binding: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_collection_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_collection_namespaced_role_binding_with_http_info(namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_collection_namespaced_role_binding_with_http_info(namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_collection_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_namespaced_role
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_namespaced_role(name, namespace, opts)
-delete a Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the Role
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  grace_period_seconds: 56, # Integer | 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: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_namespaced_role(name, namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_namespaced_role: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the Role |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## delete_rbac_authorization_v1_namespaced_role_binding
-> <IoK8sApimachineryPkgApisMetaV1Status> delete_rbac_authorization_v1_namespaced_role_binding(name, namespace, opts)
-delete a RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the RoleBinding
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  grace_period_seconds: 56, # Integer | 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: true, # Boolean | 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: 'propagation_policy_example', # String | 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.
-  body: Zilla::IoK8sApimachineryPkgApisMetaV1DeleteOptions.new # IoK8sApimachineryPkgApisMetaV1DeleteOptions |
-}
-begin
-  result = api_instance.delete_rbac_authorization_v1_namespaced_role_binding(name, namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_namespaced_role_binding: #{e}"
-end
-```
-#### Using the delete_rbac_authorization_v1_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1Status>, Integer, Hash)> delete_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.delete_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1Status>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->delete_rbac_authorization_v1_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the RoleBinding |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **grace_period_seconds** | **Integer** | 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. | [optional] |
-| **orphan_dependents** | **Boolean** | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \&quot;orphan\&quot; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both. | [optional] |
-| **propagation_policy** | **String** | 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: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground. | [optional] |
-| **body** | [**IoK8sApimachineryPkgApisMetaV1DeleteOptions**](IoK8sApimachineryPkgApisMetaV1DeleteOptions.md) |  | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1Status**](IoK8sApimachineryPkgApisMetaV1Status.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## get_rbac_authorization_v1_api_resources
-> <IoK8sApimachineryPkgApisMetaV1APIResourceList> get_rbac_authorization_v1_api_resources
-get available resources
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-begin
-  result = api_instance.get_rbac_authorization_v1_api_resources
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->get_rbac_authorization_v1_api_resources: #{e}"
-end
-```
-#### Using the get_rbac_authorization_v1_api_resources_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1APIResourceList>, Integer, Hash)> get_rbac_authorization_v1_api_resources_with_http_info
-```ruby
-begin
-  data, status_code, headers = api_instance.get_rbac_authorization_v1_api_resources_with_http_info
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1APIResourceList>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->get_rbac_authorization_v1_api_resources_with_http_info: #{e}"
-end
-```
-### Parameters
-This endpoint does not need any parameter.
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1APIResourceList**](IoK8sApimachineryPkgApisMetaV1APIResourceList.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## list_rbac_authorization_v1_cluster_role
-> <IoK8sApiRbacV1ClusterRoleList> list_rbac_authorization_v1_cluster_role(opts)
-list or watch objects of kind ClusterRole
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.list_rbac_authorization_v1_cluster_role(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_cluster_role: #{e}"
-end
-```
-#### Using the list_rbac_authorization_v1_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRoleList>, Integer, Hash)> list_rbac_authorization_v1_cluster_role_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.list_rbac_authorization_v1_cluster_role_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRoleList>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRoleList**](IoK8sApiRbacV1ClusterRoleList.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## list_rbac_authorization_v1_cluster_role_binding
-> <IoK8sApiRbacV1ClusterRoleBindingList> list_rbac_authorization_v1_cluster_role_binding(opts)
-list or watch objects of kind ClusterRoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.list_rbac_authorization_v1_cluster_role_binding(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_cluster_role_binding: #{e}"
-end
-```
-#### Using the list_rbac_authorization_v1_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRoleBindingList>, Integer, Hash)> list_rbac_authorization_v1_cluster_role_binding_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.list_rbac_authorization_v1_cluster_role_binding_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRoleBindingList>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRoleBindingList**](IoK8sApiRbacV1ClusterRoleBindingList.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## list_rbac_authorization_v1_namespaced_role
-> <IoK8sApiRbacV1RoleList> list_rbac_authorization_v1_namespaced_role(namespace, opts)
-list or watch objects of kind Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.list_rbac_authorization_v1_namespaced_role(namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_namespaced_role: #{e}"
-end
-```
-#### Using the list_rbac_authorization_v1_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleList>, Integer, Hash)> list_rbac_authorization_v1_namespaced_role_with_http_info(namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.list_rbac_authorization_v1_namespaced_role_with_http_info(namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleList>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleList**](IoK8sApiRbacV1RoleList.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## list_rbac_authorization_v1_namespaced_role_binding
-> <IoK8sApiRbacV1RoleBindingList> list_rbac_authorization_v1_namespaced_role_binding(namespace, opts)
-list or watch objects of kind RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | 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: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.list_rbac_authorization_v1_namespaced_role_binding(namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_namespaced_role_binding: #{e}"
-end
-```
-#### Using the list_rbac_authorization_v1_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleBindingList>, Integer, Hash)> list_rbac_authorization_v1_namespaced_role_binding_with_http_info(namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.list_rbac_authorization_v1_namespaced_role_binding_with_http_info(namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleBindingList>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleBindingList**](IoK8sApiRbacV1RoleBindingList.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## list_rbac_authorization_v1_role_binding_for_all_namespaces
-> <IoK8sApiRbacV1RoleBindingList> list_rbac_authorization_v1_role_binding_for_all_namespaces(opts)
-list or watch objects of kind RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.list_rbac_authorization_v1_role_binding_for_all_namespaces(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_role_binding_for_all_namespaces: #{e}"
-end
-```
-#### Using the list_rbac_authorization_v1_role_binding_for_all_namespaces_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleBindingList>, Integer, Hash)> list_rbac_authorization_v1_role_binding_for_all_namespaces_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.list_rbac_authorization_v1_role_binding_for_all_namespaces_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleBindingList>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_role_binding_for_all_namespaces_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleBindingList**](IoK8sApiRbacV1RoleBindingList.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## list_rbac_authorization_v1_role_for_all_namespaces
-> <IoK8sApiRbacV1RoleList> list_rbac_authorization_v1_role_for_all_namespaces(opts)
-list or watch objects of kind Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.list_rbac_authorization_v1_role_for_all_namespaces(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_role_for_all_namespaces: #{e}"
-end
-```
-#### Using the list_rbac_authorization_v1_role_for_all_namespaces_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleList>, Integer, Hash)> list_rbac_authorization_v1_role_for_all_namespaces_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.list_rbac_authorization_v1_role_for_all_namespaces_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleList>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->list_rbac_authorization_v1_role_for_all_namespaces_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleList**](IoK8sApiRbacV1RoleList.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## patch_rbac_authorization_v1_cluster_role
-> <IoK8sApiRbacV1ClusterRole> patch_rbac_authorization_v1_cluster_role(name, body, opts)
-partially update the specified ClusterRole
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRole
-body = { ... } # Object |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).
-  field_validation: 'field_validation_example', # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-  force: true # Boolean | Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.
-}
-begin
-  result = api_instance.patch_rbac_authorization_v1_cluster_role(name, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_cluster_role: #{e}"
-end
-```
-#### Using the patch_rbac_authorization_v1_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRole>, Integer, Hash)> patch_rbac_authorization_v1_cluster_role_with_http_info(name, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.patch_rbac_authorization_v1_cluster_role_with_http_info(name, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRole>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRole |  |
-| **body** | **Object** |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-| **force** | **Boolean** | Force is going to \&quot;force\&quot; Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRole**](IoK8sApiRbacV1ClusterRole.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json, application/apply-patch+yaml
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## patch_rbac_authorization_v1_cluster_role_binding
-> <IoK8sApiRbacV1ClusterRoleBinding> patch_rbac_authorization_v1_cluster_role_binding(name, body, opts)
-partially update the specified ClusterRoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRoleBinding
-body = { ... } # Object |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).
-  field_validation: 'field_validation_example', # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-  force: true # Boolean | Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.
-}
-begin
-  result = api_instance.patch_rbac_authorization_v1_cluster_role_binding(name, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_cluster_role_binding: #{e}"
-end
-```
-#### Using the patch_rbac_authorization_v1_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRoleBinding>, Integer, Hash)> patch_rbac_authorization_v1_cluster_role_binding_with_http_info(name, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.patch_rbac_authorization_v1_cluster_role_binding_with_http_info(name, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRoleBinding |  |
-| **body** | **Object** |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-| **force** | **Boolean** | Force is going to \&quot;force\&quot; Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRoleBinding**](IoK8sApiRbacV1ClusterRoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json, application/apply-patch+yaml
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## patch_rbac_authorization_v1_namespaced_role
-> <IoK8sApiRbacV1Role> patch_rbac_authorization_v1_namespaced_role(name, namespace, body, opts)
-partially update the specified Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the Role
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-body = { ... } # Object |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).
-  field_validation: 'field_validation_example', # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-  force: true # Boolean | Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.
-}
-begin
-  result = api_instance.patch_rbac_authorization_v1_namespaced_role(name, namespace, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_namespaced_role: #{e}"
-end
-```
-#### Using the patch_rbac_authorization_v1_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1Role>, Integer, Hash)> patch_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.patch_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1Role>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the Role |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **body** | **Object** |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-| **force** | **Boolean** | Force is going to \&quot;force\&quot; Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. | [optional] |
-### Return type
-[**IoK8sApiRbacV1Role**](IoK8sApiRbacV1Role.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json, application/apply-patch+yaml
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## patch_rbac_authorization_v1_namespaced_role_binding
-> <IoK8sApiRbacV1RoleBinding> patch_rbac_authorization_v1_namespaced_role_binding(name, namespace, body, opts)
-partially update the specified RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the RoleBinding
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-body = { ... } # Object |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch).
-  field_validation: 'field_validation_example', # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-  force: true # Boolean | Force is going to \"force\" Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests.
-}
-begin
-  result = api_instance.patch_rbac_authorization_v1_namespaced_role_binding(name, namespace, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_namespaced_role_binding: #{e}"
-end
-```
-#### Using the patch_rbac_authorization_v1_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleBinding>, Integer, Hash)> patch_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.patch_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->patch_rbac_authorization_v1_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the RoleBinding |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **body** | **Object** |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. This field is required for apply requests (application/apply-patch) but optional for non-apply patch types (JsonPatch, MergePatch, StrategicMergePatch). | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-| **force** | **Boolean** | Force is going to \&quot;force\&quot; Apply requests. It means user will re-acquire conflicting fields owned by other people. Force flag must be unset for non-apply patch requests. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleBinding**](IoK8sApiRbacV1RoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json-patch+json, application/merge-patch+json, application/strategic-merge-patch+json, application/apply-patch+yaml
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## read_rbac_authorization_v1_cluster_role
-> <IoK8sApiRbacV1ClusterRole> read_rbac_authorization_v1_cluster_role(name, opts)
-read the specified ClusterRole
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRole
-opts = {
-  pretty: 'pretty_example' # String | If 'true', then the output is pretty printed.
-}
-begin
-  result = api_instance.read_rbac_authorization_v1_cluster_role(name, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_cluster_role: #{e}"
-end
-```
-#### Using the read_rbac_authorization_v1_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRole>, Integer, Hash)> read_rbac_authorization_v1_cluster_role_with_http_info(name, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.read_rbac_authorization_v1_cluster_role_with_http_info(name, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRole>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRole |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRole**](IoK8sApiRbacV1ClusterRole.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## read_rbac_authorization_v1_cluster_role_binding
-> <IoK8sApiRbacV1ClusterRoleBinding> read_rbac_authorization_v1_cluster_role_binding(name, opts)
-read the specified ClusterRoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRoleBinding
-opts = {
-  pretty: 'pretty_example' # String | If 'true', then the output is pretty printed.
-}
-begin
-  result = api_instance.read_rbac_authorization_v1_cluster_role_binding(name, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_cluster_role_binding: #{e}"
-end
-```
-#### Using the read_rbac_authorization_v1_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRoleBinding>, Integer, Hash)> read_rbac_authorization_v1_cluster_role_binding_with_http_info(name, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.read_rbac_authorization_v1_cluster_role_binding_with_http_info(name, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRoleBinding |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRoleBinding**](IoK8sApiRbacV1ClusterRoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## read_rbac_authorization_v1_namespaced_role
-> <IoK8sApiRbacV1Role> read_rbac_authorization_v1_namespaced_role(name, namespace, opts)
-read the specified Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the Role
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example' # String | If 'true', then the output is pretty printed.
-}
-begin
-  result = api_instance.read_rbac_authorization_v1_namespaced_role(name, namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_namespaced_role: #{e}"
-end
-```
-#### Using the read_rbac_authorization_v1_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1Role>, Integer, Hash)> read_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.read_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1Role>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the Role |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-### Return type
-[**IoK8sApiRbacV1Role**](IoK8sApiRbacV1Role.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## read_rbac_authorization_v1_namespaced_role_binding
-> <IoK8sApiRbacV1RoleBinding> read_rbac_authorization_v1_namespaced_role_binding(name, namespace, opts)
-read the specified RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the RoleBinding
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  pretty: 'pretty_example' # String | If 'true', then the output is pretty printed.
-}
-begin
-  result = api_instance.read_rbac_authorization_v1_namespaced_role_binding(name, namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_namespaced_role_binding: #{e}"
-end
-```
-#### Using the read_rbac_authorization_v1_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleBinding>, Integer, Hash)> read_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.read_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->read_rbac_authorization_v1_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the RoleBinding |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleBinding**](IoK8sApiRbacV1RoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## replace_rbac_authorization_v1_cluster_role
-> <IoK8sApiRbacV1ClusterRole> replace_rbac_authorization_v1_cluster_role(name, body, opts)
-replace the specified ClusterRole
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRole
-body = Zilla::IoK8sApiRbacV1ClusterRole.new # IoK8sApiRbacV1ClusterRole |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.replace_rbac_authorization_v1_cluster_role(name, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_cluster_role: #{e}"
-end
-```
-#### Using the replace_rbac_authorization_v1_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRole>, Integer, Hash)> replace_rbac_authorization_v1_cluster_role_with_http_info(name, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.replace_rbac_authorization_v1_cluster_role_with_http_info(name, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRole>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRole |  |
-| **body** | [**IoK8sApiRbacV1ClusterRole**](IoK8sApiRbacV1ClusterRole.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRole**](IoK8sApiRbacV1ClusterRole.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## replace_rbac_authorization_v1_cluster_role_binding
-> <IoK8sApiRbacV1ClusterRoleBinding> replace_rbac_authorization_v1_cluster_role_binding(name, body, opts)
-replace the specified ClusterRoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRoleBinding
-body = Zilla::IoK8sApiRbacV1ClusterRoleBinding.new({role_ref: Zilla::IoK8sApiRbacV1RoleRef.new({api_group: 'api_group_example', kind: 'kind_example', name: 'name_example'})}) # IoK8sApiRbacV1ClusterRoleBinding |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.replace_rbac_authorization_v1_cluster_role_binding(name, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_cluster_role_binding: #{e}"
-end
-```
-#### Using the replace_rbac_authorization_v1_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1ClusterRoleBinding>, Integer, Hash)> replace_rbac_authorization_v1_cluster_role_binding_with_http_info(name, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.replace_rbac_authorization_v1_cluster_role_binding_with_http_info(name, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1ClusterRoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRoleBinding |  |
-| **body** | [**IoK8sApiRbacV1ClusterRoleBinding**](IoK8sApiRbacV1ClusterRoleBinding.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1ClusterRoleBinding**](IoK8sApiRbacV1ClusterRoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## replace_rbac_authorization_v1_namespaced_role
-> <IoK8sApiRbacV1Role> replace_rbac_authorization_v1_namespaced_role(name, namespace, body, opts)
-replace the specified Role
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the Role
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-body = Zilla::IoK8sApiRbacV1Role.new # IoK8sApiRbacV1Role |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.replace_rbac_authorization_v1_namespaced_role(name, namespace, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_namespaced_role: #{e}"
-end
-```
-#### Using the replace_rbac_authorization_v1_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1Role>, Integer, Hash)> replace_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.replace_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1Role>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the Role |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **body** | [**IoK8sApiRbacV1Role**](IoK8sApiRbacV1Role.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1Role**](IoK8sApiRbacV1Role.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## replace_rbac_authorization_v1_namespaced_role_binding
-> <IoK8sApiRbacV1RoleBinding> replace_rbac_authorization_v1_namespaced_role_binding(name, namespace, body, opts)
-replace the specified RoleBinding
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the RoleBinding
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-body = Zilla::IoK8sApiRbacV1RoleBinding.new({role_ref: Zilla::IoK8sApiRbacV1RoleRef.new({api_group: 'api_group_example', kind: 'kind_example', name: 'name_example'})}) # IoK8sApiRbacV1RoleBinding |
-opts = {
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  dry_run: 'dry_run_example', # String | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
-  field_manager: 'field_manager_example', # String | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint.
-  field_validation: 'field_validation_example' # String | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the `ServerSideFieldValidation` feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the `ServerSideFieldValidation` feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the `ServerSideFieldValidation` feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.
-}
-begin
-  result = api_instance.replace_rbac_authorization_v1_namespaced_role_binding(name, namespace, body, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_namespaced_role_binding: #{e}"
-end
-```
-#### Using the replace_rbac_authorization_v1_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApiRbacV1RoleBinding>, Integer, Hash)> replace_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, body, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.replace_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, body, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApiRbacV1RoleBinding>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->replace_rbac_authorization_v1_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the RoleBinding |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **body** | [**IoK8sApiRbacV1RoleBinding**](IoK8sApiRbacV1RoleBinding.md) |  |  |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **dry_run** | **String** | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed | [optional] |
-| **field_manager** | **String** | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. | [optional] |
-| **field_validation** | **String** | fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the &#x60;ServerSideFieldValidation&#x60; feature gate is also enabled. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23 and is the default behavior when the &#x60;ServerSideFieldValidation&#x60; feature gate is disabled. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default when the &#x60;ServerSideFieldValidation&#x60; feature gate is enabled. - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. | [optional] |
-### Return type
-[**IoK8sApiRbacV1RoleBinding**](IoK8sApiRbacV1RoleBinding.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf
-## watch_rbac_authorization_v1_cluster_role
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_cluster_role(name, opts)
-watch changes to an object of kind ClusterRole. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRole
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_cluster_role(name, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_cluster_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_cluster_role_with_http_info(name, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_cluster_role_with_http_info(name, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRole |  |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_cluster_role_binding
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_cluster_role_binding(name, opts)
-watch changes to an object of kind ClusterRoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the ClusterRoleBinding
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_cluster_role_binding(name, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role_binding: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_cluster_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_cluster_role_binding_with_http_info(name, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_cluster_role_binding_with_http_info(name, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the ClusterRoleBinding |  |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_cluster_role_binding_list
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_cluster_role_binding_list(opts)
-watch individual changes to a list of ClusterRoleBinding. deprecated: use the 'watch' parameter with a list operation instead.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_cluster_role_binding_list(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role_binding_list: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_cluster_role_binding_list_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_cluster_role_binding_list_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_cluster_role_binding_list_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role_binding_list_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_cluster_role_list
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_cluster_role_list(opts)
-watch individual changes to a list of ClusterRole. deprecated: use the 'watch' parameter with a list operation instead.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_cluster_role_list(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role_list: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_cluster_role_list_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_cluster_role_list_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_cluster_role_list_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_cluster_role_list_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_namespaced_role
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_namespaced_role(name, namespace, opts)
-watch changes to an object of kind Role. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the Role
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_namespaced_role(name, namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_namespaced_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_namespaced_role_with_http_info(name, namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the Role |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_namespaced_role_binding
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_namespaced_role_binding(name, namespace, opts)
-watch changes to an object of kind RoleBinding. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-name = 'name_example' # String | name of the RoleBinding
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_namespaced_role_binding(name, namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role_binding: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_namespaced_role_binding_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_namespaced_role_binding_with_http_info(name, namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role_binding_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **name** | **String** | name of the RoleBinding |  |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_namespaced_role_binding_list
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_namespaced_role_binding_list(namespace, opts)
-watch individual changes to a list of RoleBinding. deprecated: use the 'watch' parameter with a list operation instead.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_namespaced_role_binding_list(namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role_binding_list: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_namespaced_role_binding_list_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_namespaced_role_binding_list_with_http_info(namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_namespaced_role_binding_list_with_http_info(namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role_binding_list_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_namespaced_role_list
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_namespaced_role_list(namespace, opts)
-watch individual changes to a list of Role. deprecated: use the 'watch' parameter with a list operation instead.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-namespace = 'namespace_example' # String | object name and auth scope, such as for teams and projects
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_namespaced_role_list(namespace, opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role_list: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_namespaced_role_list_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_namespaced_role_list_with_http_info(namespace, opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_namespaced_role_list_with_http_info(namespace, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_namespaced_role_list_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **namespace** | **String** | object name and auth scope, such as for teams and projects |  |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_role_binding_list_for_all_namespaces
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_role_binding_list_for_all_namespaces(opts)
-watch individual changes to a list of RoleBinding. deprecated: use the 'watch' parameter with a list operation instead.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_role_binding_list_for_all_namespaces(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_role_binding_list_for_all_namespaces: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_role_binding_list_for_all_namespaces_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_role_binding_list_for_all_namespaces_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_role_binding_list_for_all_namespaces_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_role_binding_list_for_all_namespaces_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch
-## watch_rbac_authorization_v1_role_list_for_all_namespaces
-> <IoK8sApimachineryPkgApisMetaV1WatchEvent> watch_rbac_authorization_v1_role_list_for_all_namespaces(opts)
-watch individual changes to a list of Role. deprecated: use the 'watch' parameter with a list operation instead.
-### Examples
-```ruby
-require 'time'
-require 'zilla'
-# setup authorization
-Zilla.configure do |config|
-  # Configure API key authorization: BearerToken
-  config.api_key['BearerToken'] = 'YOUR API KEY'
-  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
-  # config.api_key_prefix['BearerToken'] = 'Bearer'
-end
-api_instance = Zilla::RbacAuthorizationV1Api.new
-opts = {
-  allow_watch_bookmarks: true, # Boolean | allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored.
-  continue: 'continue_example', # String | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".  This field is not 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: 'field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything.
-  label_selector: 'label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything.
-  limit: 56, # Integer | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
-  pretty: 'pretty_example', # String | If 'true', then the output is pretty printed.
-  resource_version: 'resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  resource_version_match: 'resource_version_match_example', # String | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset
-  timeout_seconds: 56, # Integer | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
-  watch: true # Boolean | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
-}
-begin
-  result = api_instance.watch_rbac_authorization_v1_role_list_for_all_namespaces(opts)
-  p result
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_role_list_for_all_namespaces: #{e}"
-end
-```
-#### Using the watch_rbac_authorization_v1_role_list_for_all_namespaces_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<IoK8sApimachineryPkgApisMetaV1WatchEvent>, Integer, Hash)> watch_rbac_authorization_v1_role_list_for_all_namespaces_with_http_info(opts)
-```ruby
-begin
-  data, status_code, headers = api_instance.watch_rbac_authorization_v1_role_list_for_all_namespaces_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <IoK8sApimachineryPkgApisMetaV1WatchEvent>
-rescue Zilla::ApiError => e
-  puts "Error when calling RbacAuthorizationV1Api->watch_rbac_authorization_v1_role_list_for_all_namespaces_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **allow_watch_bookmarks** | **Boolean** | allowWatchBookmarks requests watch events with type \&quot;BOOKMARK\&quot;. Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server&#39;s discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | [optional] |
-| **continue** | **String** | The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \&quot;next key\&quot;.  This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | [optional] |
-| **field_selector** | **String** | A selector to restrict the list of returned objects by their fields. Defaults to everything. | [optional] |
-| **label_selector** | **String** | A selector to restrict the list of returned objects by their labels. Defaults to everything. | [optional] |
-| **limit** | **Integer** | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the &#x60;continue&#x60; field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true.  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
-| **pretty** | **String** | If &#39;true&#39;, then the output is pretty printed. | [optional] |
-| **resource_version** | **String** | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **resource_version_match** | **String** | resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.  Defaults to unset | [optional] |
-| **timeout_seconds** | **Integer** | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. | [optional] |
-| **watch** | **Boolean** | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. | [optional] |
-### Return type
-[**IoK8sApimachineryPkgApisMetaV1WatchEvent**](IoK8sApimachineryPkgApisMetaV1WatchEvent.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json, application/yaml, application/vnd.kubernetes.protobuf, application/json;stream=watch, application/vnd.kubernetes.protobuf;stream=watch