Puppet Task: swagger_k8s_delete_core_v1_collection_node
- Defined in:
-
tasks/swagger_k8s_delete_core_v1_collection_node.json,
tasks/swagger_k8s_delete_core_v1_collection_node.rb
Overview
delete collection of Node
Supports noop? false
Parameters
- kube_api (String) — Kubernetes API endpoint
- ca_file (Optional[String[1]]) — Certificate file path
-
token
(Optional[String[1]])
— Authentication token obtained from 'kubectl describe secret
' - pretty (Optional[String[1]]) — If 'true', then the output is pretty printed.
- apiversion (Optional[String[1]]) — APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources
- kind (Optional[String[1]]) — Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds
- label_selector (Optional[String[1]]) — A selector to restrict the list of returned objects by their labels. Defaults to everything.
- limit (Optional[String[1]]) — 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.
- timeout_seconds (Optional[String[1]]) — Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
- watch (Optional[String[1]]) — Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.
- metadata (Optional[String[1]]) — Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
- spec (Optional[String[1]]) — Spec defines the behavior of a node. https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status
- status (Optional[String[1]]) — Most recently observed status of the node. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status
- continue (Optional[String[1]]) — 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 (Optional[String[1]]) — A selector to restrict the list of returned objects by their fields. Defaults to everything.
- resource_version (Optional[String[1]]) — When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.