Struct k8s_openapi::v1_8::api::core::v1::Node

pub struct Node {
    pub api_version: Option<String>,
    pub kind: Option<String>,
    pub metadata: Option<ObjectMeta>,
    pub spec: Option<NodeSpec>,
    pub status: Option<NodeStatus>,
}

Node is a worker node in Kubernetes. Each node will have a unique identifier in the cache (i.e. in etcd).

Fields

api_version: Option<String>

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: Option<String>

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

metadata: Option<ObjectMeta>

Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata

spec: Option<NodeSpec>

Spec defines the behavior of a node. https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status

status: Option<NodeStatus>

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

Implementations

impl Node

pub fn connect_core_v1_delete_node_proxy(
    name: &str,
    path: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect DELETE requests to proxy of Node

Use ConnectCoreV1DeleteNodeProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_delete_node_proxy_with_path(
    name: &str,
    path: &str,
    path_: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect DELETE requests to proxy of Node

Use ConnectCoreV1DeleteNodeProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

• path_

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_get_node_proxy(
    name: &str,
    path: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect GET requests to proxy of Node

Use ConnectCoreV1GetNodeProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_get_node_proxy_with_path(
    name: &str,
    path: &str,
    path_: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect GET requests to proxy of Node

Use ConnectCoreV1GetNodeProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

• path_

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_patch_node_proxy(
    name: &str,
    path: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect PATCH requests to proxy of Node

Use ConnectCoreV1PatchNodeProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_patch_node_proxy_with_path(
    name: &str,
    path: &str,
    path_: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect PATCH requests to proxy of Node

Use ConnectCoreV1PatchNodeProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

• path_

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_post_node_proxy(
    name: &str,
    path: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect POST requests to proxy of Node

Use ConnectCoreV1PostNodeProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_post_node_proxy_with_path(
    name: &str,
    path: &str,
    path_: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect POST requests to proxy of Node

Use ConnectCoreV1PostNodeProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

• path_

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_put_node_proxy(
    name: &str,
    path: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect PUT requests to proxy of Node

Use ConnectCoreV1PutNodeProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn connect_core_v1_put_node_proxy_with_path(
    name: &str,
    path: &str,
    path_: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

connect PUT requests to proxy of Node

Use ConnectCoreV1PutNodeProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

• path_

  Path is the URL path to use for the current proxy request to node.

impl Node

pub fn create_core_v1_node(
    body: &Node,
    pretty: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

create a Node

Use CreateCoreV1NodeResponse to parse the HTTP response.

Arguments

• body

• pretty

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

impl Node

pub fn delete_core_v1_collection_node(
    continue_: Option<&str>,
    field_selector: Option<&str>,
    include_uninitialized: Option<bool>,
    label_selector: Option<&str>,
    limit: Option<i64>,
    pretty: Option<&str>,
    resource_version: Option<&str>,
    timeout_seconds: Option<i64>,
    watch: Option<bool>
) -> Result<Request<Vec<u8>>, RequestError>

delete collection of Node

Use DeleteCoreV1CollectionNodeResponse to parse the HTTP response.

Arguments

• continue_

  The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

• field_selector

  A selector to restrict the list of returned objects by their fields. Defaults to everything.

• include_uninitialized

  If true, partially initialized resources are included in the response.

• label_selector

  A selector to restrict the list of returned objects by their labels. Defaults to everything.

• limit

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

  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

• pretty

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

• resource_version

  When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.

• timeout_seconds

  Timeout for the list/watch call.

• watch

  Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.

impl Node

pub fn delete_core_v1_node(
    name: &str,
    grace_period_seconds: Option<i64>,
    orphan_dependents: Option<bool>,
    pretty: Option<&str>,
    propagation_policy: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

delete a Node

Use DeleteCoreV1NodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• body

• grace_period_seconds

  The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.

• orphan_dependents

  Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the “orphan” finalizer will be added to/removed from the object’s finalizers list. Either this field or PropagationPolicy may be set, but not both.

• pretty

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

• propagation_policy

  Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy.

impl Node

pub fn list_core_v1_node(
    continue_: Option<&str>,
    field_selector: Option<&str>,
    include_uninitialized: Option<bool>,
    label_selector: Option<&str>,
    limit: Option<i64>,
    pretty: Option<&str>,
    resource_version: Option<&str>,
    timeout_seconds: Option<i64>,
    watch: Option<bool>
) -> Result<Request<Vec<u8>>, RequestError>

list or watch objects of kind Node

Use ListCoreV1NodeResponse to parse the HTTP response.

Arguments

• continue_

  The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

• field_selector

  A selector to restrict the list of returned objects by their fields. Defaults to everything.

• include_uninitialized

  If true, partially initialized resources are included in the response.

• label_selector

  A selector to restrict the list of returned objects by their labels. Defaults to everything.

• limit

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

  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

• pretty

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

• resource_version

  When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.

• timeout_seconds

  Timeout for the list/watch call.

• watch

  Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.

impl Node

pub fn patch_core_v1_node(
    name: &str,
    body: &Patch,
    pretty: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

partially update the specified Node

Use PatchCoreV1NodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• body

• pretty

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

impl Node

pub fn patch_core_v1_node_status(
    name: &str,
    body: &Patch,
    pretty: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

partially update status of the specified Node

Use PatchCoreV1NodeStatusResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• body

• pretty

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

impl Node

pub fn proxy_core_v1_delete_node(
    name: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy DELETE requests to Node

Use ProxyCoreV1DELETENodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

impl Node

pub fn proxy_core_v1_delete_node_with_path(
    name: &str,
    path: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy DELETE requests to Node

Use ProxyCoreV1DELETENodeWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

impl Node

pub fn proxy_core_v1_get_node(
    name: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy GET requests to Node

Use ProxyCoreV1GETNodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

impl Node

pub fn proxy_core_v1_get_node_with_path(
    name: &str,
    path: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy GET requests to Node

Use ProxyCoreV1GETNodeWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

impl Node

pub fn proxy_core_v1_patch_node(
    name: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy PATCH requests to Node

Use ProxyCoreV1PATCHNodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

impl Node

pub fn proxy_core_v1_patch_node_with_path(
    name: &str,
    path: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy PATCH requests to Node

Use ProxyCoreV1PATCHNodeWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

impl Node

pub fn proxy_core_v1_post_node(
    name: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy POST requests to Node

Use ProxyCoreV1POSTNodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

impl Node

pub fn proxy_core_v1_post_node_with_path(
    name: &str,
    path: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy POST requests to Node

Use ProxyCoreV1POSTNodeWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

impl Node

pub fn proxy_core_v1_put_node(
    name: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy PUT requests to Node

Use ProxyCoreV1PUTNodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

impl Node

pub fn proxy_core_v1_put_node_with_path(
    name: &str,
    path: &str
) -> Result<Request<Vec<u8>>, RequestError>

proxy PUT requests to Node

Use ProxyCoreV1PUTNodeWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• path

  path to the resource

impl Node

pub fn read_core_v1_node(
    name: &str,
    exact: Option<bool>,
    export: Option<bool>,
    pretty: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

read the specified Node

Use ReadCoreV1NodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• exact

  Should the export be exact. Exact export maintains cluster-specific fields like ‘Namespace’.

• export

  Should this value be exported. Export strips fields that a user can not specify.

• pretty

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

impl Node

pub fn read_core_v1_node_status(
    name: &str,
    pretty: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

read status of the specified Node

Use ReadCoreV1NodeStatusResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• pretty

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

impl Node

pub fn replace_core_v1_node(
    name: &str,
    body: &Node,
    pretty: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

replace the specified Node

Use ReplaceCoreV1NodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• body

• pretty

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

impl Node

pub fn replace_core_v1_node_status(
    name: &str,
    body: &Node,
    pretty: Option<&str>
) -> Result<Request<Vec<u8>>, RequestError>

replace status of the specified Node

Use ReplaceCoreV1NodeStatusResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• body

• pretty

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

impl Node

pub fn watch_core_v1_node(
    name: &str,
    continue_: Option<&str>,
    field_selector: Option<&str>,
    include_uninitialized: Option<bool>,
    label_selector: Option<&str>,
    limit: Option<i64>,
    pretty: Option<&str>,
    resource_version: Option<&str>,
    timeout_seconds: Option<i64>,
    watch: Option<bool>
) -> Result<Request<Vec<u8>>, RequestError>

watch changes to an object of kind Node

Use WatchCoreV1NodeResponse to parse the HTTP response.

Arguments

• name

  name of the Node

• continue_

  The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

• field_selector

  A selector to restrict the list of returned objects by their fields. Defaults to everything.

• include_uninitialized

  If true, partially initialized resources are included in the response.

• label_selector

  A selector to restrict the list of returned objects by their labels. Defaults to everything.

• limit

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

  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

• pretty

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

• resource_version

  When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.

• timeout_seconds

  Timeout for the list/watch call.

• watch

  Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.

impl Node

pub fn watch_core_v1_node_list(
    continue_: Option<&str>,
    field_selector: Option<&str>,
    include_uninitialized: Option<bool>,
    label_selector: Option<&str>,
    limit: Option<i64>,
    pretty: Option<&str>,
    resource_version: Option<&str>,
    timeout_seconds: Option<i64>,
    watch: Option<bool>
) -> Result<Request<Vec<u8>>, RequestError>

watch individual changes to a list of Node

Use WatchCoreV1NodeListResponse to parse the HTTP response.

Arguments

• continue_

  The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.

• field_selector

  A selector to restrict the list of returned objects by their fields. Defaults to everything.

• include_uninitialized

  If true, partially initialized resources are included in the response.

• label_selector

  A selector to restrict the list of returned objects by their labels. Defaults to everything.

• limit

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

  The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.

• pretty

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

• resource_version

  When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it’s 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.

• timeout_seconds

  Timeout for the list/watch call.

• watch

  Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.

Trait Implementations

impl Clone for Node

fn clone(&self) -> Node

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Node

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Node

fn default() -> Node

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for Node

fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>where
    D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq<Node> for Node

fn eq(&self, other: &Node) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for Node

fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>where
    S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for Node