Struct k8s_openapi::v1_11::api::core::v1::Pod

pub struct Pod {
    pub api_version: Option<String>,
    pub kind: Option<String>,
    pub metadata: Option<ObjectMeta>,
    pub spec: Option<PodSpec>,
    pub status: Option<PodStatus>,
}

Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts.

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<PodSpec>

Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status

status: Option<PodStatus>

Most recently observed status of the pod. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status

Methods

impl Pod

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

connect DELETE requests to proxy of Pod

Use ConnectCoreV1DeleteNamespacedPodProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

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

impl Pod

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

connect DELETE requests to proxy of Pod

Use ConnectCoreV1DeleteNamespacedPodProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

  path to the resource

• path_

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

impl Pod

pub fn connect_core_v1_get_namespaced_pod_attach(     name: &str,     namespace: &str,     container: Option<&str>,     stderr: Option<bool>,     stdin: Option<bool>,     stdout: Option<bool>,     tty: Option<bool> ) -> Result<Request<Vec<u8>>, RequestError>

connect GET requests to attach of Pod

Use ConnectCoreV1GetNamespacedPodAttachResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• container

  The container in which to execute the command. Defaults to only container if there is only one container in the pod.

• stderr

  Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true.

• stdin

  Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false.

• stdout

  Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true.

• tty

  TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. Defaults to false.

impl Pod

pub fn connect_core_v1_get_namespaced_pod_exec(     name: &str,     namespace: &str,     command: Option<&str>,     container: Option<&str>,     stderr: Option<bool>,     stdin: Option<bool>,     stdout: Option<bool>,     tty: Option<bool> ) -> Result<Request<Vec<u8>>, RequestError>

connect GET requests to exec of Pod

Use ConnectCoreV1GetNamespacedPodExecResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• command

  Command is the remote command to execute. argv array. Not executed within a shell.

• container

  Container in which to execute the command. Defaults to only container if there is only one container in the pod.

• stderr

  Redirect the standard error stream of the pod for this call. Defaults to true.

• stdin

  Redirect the standard input stream of the pod for this call. Defaults to false.

• stdout

  Redirect the standard output stream of the pod for this call. Defaults to true.

• tty

  TTY if true indicates that a tty will be allocated for the exec call. Defaults to false.

impl Pod

pub fn connect_core_v1_get_namespaced_pod_portforward(     name: &str,     namespace: &str,     ports: Option<i64> ) -> Result<Request<Vec<u8>>, RequestError>

connect GET requests to portforward of Pod

Use ConnectCoreV1GetNamespacedPodPortforwardResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• ports

  List of ports to forward Required when using WebSockets

impl Pod

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

connect GET requests to proxy of Pod

Use ConnectCoreV1GetNamespacedPodProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

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

impl Pod

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

connect GET requests to proxy of Pod

Use ConnectCoreV1GetNamespacedPodProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

  path to the resource

• path_

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

impl Pod

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

connect PATCH requests to proxy of Pod

Use ConnectCoreV1PatchNamespacedPodProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

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

impl Pod

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

connect PATCH requests to proxy of Pod

Use ConnectCoreV1PatchNamespacedPodProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

  path to the resource

• path_

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

impl Pod

pub fn connect_core_v1_post_namespaced_pod_attach(     name: &str,     namespace: &str,     container: Option<&str>,     stderr: Option<bool>,     stdin: Option<bool>,     stdout: Option<bool>,     tty: Option<bool> ) -> Result<Request<Vec<u8>>, RequestError>

connect POST requests to attach of Pod

Use ConnectCoreV1PostNamespacedPodAttachResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• container

  The container in which to execute the command. Defaults to only container if there is only one container in the pod.

• stderr

  Stderr if true indicates that stderr is to be redirected for the attach call. Defaults to true.

• stdin

  Stdin if true, redirects the standard input stream of the pod for this call. Defaults to false.

• stdout

  Stdout if true indicates that stdout is to be redirected for the attach call. Defaults to true.

• tty

  TTY if true indicates that a tty will be allocated for the attach call. This is passed through the container runtime so the tty is allocated on the worker node by the container runtime. Defaults to false.

impl Pod

pub fn connect_core_v1_post_namespaced_pod_exec(     name: &str,     namespace: &str,     command: Option<&str>,     container: Option<&str>,     stderr: Option<bool>,     stdin: Option<bool>,     stdout: Option<bool>,     tty: Option<bool> ) -> Result<Request<Vec<u8>>, RequestError>

connect POST requests to exec of Pod

Use ConnectCoreV1PostNamespacedPodExecResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• command

  Command is the remote command to execute. argv array. Not executed within a shell.

• container

  Container in which to execute the command. Defaults to only container if there is only one container in the pod.

• stderr

  Redirect the standard error stream of the pod for this call. Defaults to true.

• stdin

  Redirect the standard input stream of the pod for this call. Defaults to false.

• stdout

  Redirect the standard output stream of the pod for this call. Defaults to true.

• tty

  TTY if true indicates that a tty will be allocated for the exec call. Defaults to false.

impl Pod

pub fn connect_core_v1_post_namespaced_pod_portforward(     name: &str,     namespace: &str,     ports: Option<i64> ) -> Result<Request<Vec<u8>>, RequestError>

connect POST requests to portforward of Pod

Use ConnectCoreV1PostNamespacedPodPortforwardResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• ports

  List of ports to forward Required when using WebSockets

impl Pod

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

connect POST requests to proxy of Pod

Use ConnectCoreV1PostNamespacedPodProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

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

impl Pod

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

connect POST requests to proxy of Pod

Use ConnectCoreV1PostNamespacedPodProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

  path to the resource

• path_

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

impl Pod

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

connect PUT requests to proxy of Pod

Use ConnectCoreV1PutNamespacedPodProxyResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

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

impl Pod

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

connect PUT requests to proxy of Pod

Use ConnectCoreV1PutNamespacedPodProxyWithPathResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• path

  path to the resource

• path_

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

impl Pod

pub fn create_core_v1_namespaced_pod(     namespace: &str,     body: &Pod,     pretty: Option<&str> ) -> Result<Request<Vec<u8>>, RequestError>

create a Pod

Use CreateCoreV1NamespacedPodResponse to parse the HTTP response.

Arguments

• namespace

  object name and auth scope, such as for teams and projects

• body

• pretty

  If 'true', then the output is pretty printed.

impl Pod

pub fn delete_core_v1_collection_namespaced_pod(     namespace: &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>

delete collection of Pod

Use DeleteCoreV1CollectionNamespacedPodResponse to parse the HTTP response.

Arguments

• namespace

  object name and auth scope, such as for teams and projects

• 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. This limits the duration of the call, regardless of any activity or inactivity.

• watch

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

impl Pod

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

delete a Pod

Use DeleteCoreV1NamespacedPodResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• 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. 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.

impl Pod

pub fn list_core_v1_namespaced_pod(     namespace: &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>

list or watch objects of kind Pod

Use ListCoreV1NamespacedPodResponse to parse the HTTP response.

Arguments

• namespace

  object name and auth scope, such as for teams and projects

• 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. This limits the duration of the call, regardless of any activity or inactivity.

• watch

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

impl Pod

pub fn list_core_v1_pod_for_all_namespaces(     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 Pod

Use ListCoreV1PodForAllNamespacesResponse 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. This limits the duration of the call, regardless of any activity or inactivity.

• watch

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

impl Pod

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

partially update the specified Pod

Use PatchCoreV1NamespacedPodResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• body

• pretty

  If 'true', then the output is pretty printed.

impl Pod

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

partially update status of the specified Pod

Use PatchCoreV1NamespacedPodStatusResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• body

• pretty

  If 'true', then the output is pretty printed.

impl Pod

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

read the specified Pod

Use ReadCoreV1NamespacedPodResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• 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 Pod

pub fn read_core_v1_namespaced_pod_log(     name: &str,     namespace: &str,     container: Option<&str>,     follow: Option<bool>,     limit_bytes: Option<i64>,     pretty: Option<&str>,     previous: Option<bool>,     since_seconds: Option<i64>,     tail_lines: Option<i64>,     timestamps: Option<bool> ) -> Result<Request<Vec<u8>>, RequestError>

read log of the specified Pod

Use ReadCoreV1NamespacedPodLogResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• container

  The container for which to stream logs. Defaults to only container if there is one container in the pod.

• follow

  Follow the log stream of the pod. Defaults to false.

• limit_bytes

  If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit.

• pretty

  If 'true', then the output is pretty printed.

• previous

  Return previous terminated container logs. Defaults to false.

• since_seconds

  A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.

• tail_lines

  If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime

• timestamps

  If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false.

impl Pod

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

read status of the specified Pod

Use ReadCoreV1NamespacedPodStatusResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• pretty

  If 'true', then the output is pretty printed.

impl Pod

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

replace the specified Pod

Use ReplaceCoreV1NamespacedPodResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• body

• pretty

  If 'true', then the output is pretty printed.

impl Pod

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

replace status of the specified Pod

Use ReplaceCoreV1NamespacedPodStatusResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• body

• pretty

  If 'true', then the output is pretty printed.

impl Pod

pub fn watch_core_v1_namespaced_pod(     name: &str,     namespace: &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 Pod

Use WatchCoreV1NamespacedPodResponse to parse the HTTP response.

Arguments

• name

  name of the Pod

• namespace

  object name and auth scope, such as for teams and projects

• 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. This limits the duration of the call, regardless of any activity or inactivity.

• watch

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

impl Pod

pub fn watch_core_v1_namespaced_pod_list(     namespace: &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 individual changes to a list of Pod

Use WatchCoreV1NamespacedPodListResponse to parse the HTTP response.

Arguments

• namespace

  object name and auth scope, such as for teams and projects

• 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. This limits the duration of the call, regardless of any activity or inactivity.

• watch

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

impl Pod

pub fn watch_core_v1_pod_list_for_all_namespaces(     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 Pod

Use WatchCoreV1PodListForAllNamespacesResponse 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. This limits the duration of the call, regardless of any activity or inactivity.

• 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 Pod

fn clone(&self) -> Pod

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for Pod

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

Formats the value using the given formatter.

impl Default for Pod

fn default() -> Pod

Returns the "default value" for a type.

impl PartialEq for Pod

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

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

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

This method tests for !=.

impl<'de> Deserialize<'de> for Pod

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

Deserialize this value from the given Serde deserializer.

impl Serialize for Pod

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

Serialize this value into the given Serde serializer.