connect DELETE requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1DeleteNamespacedPodProxy

Parameters

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

Options

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

connect DELETE requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1DeleteNamespacedPodProxy

Parameters

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

Options

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

connect DELETE requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1DeleteNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect DELETE requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1DeleteNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect DELETE requests to proxy of Service

OpenAPI Operation ID: connectCoreV1DeleteNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect DELETE requests to proxy of Service

OpenAPI Operation ID: connectCoreV1DeleteNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect DELETE requests to proxy of Service

OpenAPI Operation ID: connectCoreV1DeleteNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect DELETE requests to proxy of Service

OpenAPI Operation ID: connectCoreV1DeleteNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect DELETE requests to proxy of Node

OpenAPI Operation ID: connectCoreV1DeleteNodeProxy

Parameters

• name - name of the Node

Options

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

connect DELETE requests to proxy of Node

OpenAPI Operation ID: connectCoreV1DeleteNodeProxy

Parameters

• name - name of the Node

Options

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

connect DELETE requests to proxy of Node

OpenAPI Operation ID: connectCoreV1DeleteNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect DELETE requests to proxy of Node

OpenAPI Operation ID: connectCoreV1DeleteNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect GET requests to attach of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodAttach

Parameters

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

Options

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

connect GET requests to attach of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodAttach

Parameters

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

Options

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

connect GET requests to exec of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodExec

Parameters

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

Options

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

connect GET requests to exec of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodExec

Parameters

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

Options

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

connect GET requests to portforward of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodPortforward

Parameters

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

Options

• ports - List of ports to forward Required when using WebSockets

connect GET requests to portforward of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodPortforward

Parameters

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

Options

• ports - List of ports to forward Required when using WebSockets

connect GET requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodProxy

Parameters

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

Options

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

connect GET requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodProxy

Parameters

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

Options

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

connect GET requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect GET requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1GetNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect GET requests to proxy of Service

OpenAPI Operation ID: connectCoreV1GetNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect GET requests to proxy of Service

OpenAPI Operation ID: connectCoreV1GetNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect GET requests to proxy of Service

OpenAPI Operation ID: connectCoreV1GetNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect GET requests to proxy of Service

OpenAPI Operation ID: connectCoreV1GetNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect GET requests to proxy of Node

OpenAPI Operation ID: connectCoreV1GetNodeProxy

Parameters

• name - name of the Node

Options

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

connect GET requests to proxy of Node

OpenAPI Operation ID: connectCoreV1GetNodeProxy

Parameters

• name - name of the Node

Options

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

connect GET requests to proxy of Node

OpenAPI Operation ID: connectCoreV1GetNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect GET requests to proxy of Node

OpenAPI Operation ID: connectCoreV1GetNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect HEAD requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1HeadNamespacedPodProxy

Parameters

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

Options

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

connect HEAD requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1HeadNamespacedPodProxy

Parameters

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

Options

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

connect HEAD requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1HeadNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect HEAD requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1HeadNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect HEAD requests to proxy of Service

OpenAPI Operation ID: connectCoreV1HeadNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect HEAD requests to proxy of Service

OpenAPI Operation ID: connectCoreV1HeadNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect HEAD requests to proxy of Service

OpenAPI Operation ID: connectCoreV1HeadNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect HEAD requests to proxy of Service

OpenAPI Operation ID: connectCoreV1HeadNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect HEAD requests to proxy of Node

OpenAPI Operation ID: connectCoreV1HeadNodeProxy

Parameters

• name - name of the Node

Options

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

connect HEAD requests to proxy of Node

OpenAPI Operation ID: connectCoreV1HeadNodeProxy

Parameters

• name - name of the Node

Options

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

connect HEAD requests to proxy of Node

OpenAPI Operation ID: connectCoreV1HeadNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect HEAD requests to proxy of Node

OpenAPI Operation ID: connectCoreV1HeadNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect OPTIONS requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1OptionsNamespacedPodProxy

Parameters

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

Options

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

connect OPTIONS requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1OptionsNamespacedPodProxy

Parameters

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

Options

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

connect OPTIONS requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1OptionsNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect OPTIONS requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1OptionsNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect OPTIONS requests to proxy of Service

OpenAPI Operation ID: connectCoreV1OptionsNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect OPTIONS requests to proxy of Service

OpenAPI Operation ID: connectCoreV1OptionsNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect OPTIONS requests to proxy of Service

OpenAPI Operation ID: connectCoreV1OptionsNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect OPTIONS requests to proxy of Service

OpenAPI Operation ID: connectCoreV1OptionsNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect OPTIONS requests to proxy of Node

OpenAPI Operation ID: connectCoreV1OptionsNodeProxy

Parameters

• name - name of the Node

Options

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

connect OPTIONS requests to proxy of Node

OpenAPI Operation ID: connectCoreV1OptionsNodeProxy

Parameters

• name - name of the Node

Options

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

connect OPTIONS requests to proxy of Node

OpenAPI Operation ID: connectCoreV1OptionsNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect OPTIONS requests to proxy of Node

OpenAPI Operation ID: connectCoreV1OptionsNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect PATCH requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PatchNamespacedPodProxy

Parameters

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

Options

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

connect PATCH requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PatchNamespacedPodProxy

Parameters

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

Options

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

connect PATCH requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PatchNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect PATCH requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PatchNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect PATCH requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PatchNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PATCH requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PatchNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PATCH requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PatchNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PATCH requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PatchNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PATCH requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PatchNodeProxy

Parameters

• name - name of the Node

Options

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

connect PATCH requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PatchNodeProxy

Parameters

• name - name of the Node

Options

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

connect PATCH requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PatchNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect PATCH requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PatchNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect POST requests to attach of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodAttach

Parameters

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

Options

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

connect POST requests to attach of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodAttach

Parameters

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

Options

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

connect POST requests to exec of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodExec

Parameters

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

Options

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

connect POST requests to exec of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodExec

Parameters

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

Options

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

connect POST requests to portforward of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodPortforward

Parameters

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

Options

• ports - List of ports to forward Required when using WebSockets

connect POST requests to portforward of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodPortforward

Parameters

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

Options

• ports - List of ports to forward Required when using WebSockets

connect POST requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodProxy

Parameters

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

Options

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

connect POST requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodProxy

Parameters

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

Options

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

connect POST requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect POST requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PostNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect POST requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PostNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect POST requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PostNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect POST requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PostNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect POST requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PostNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect POST requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PostNodeProxy

Parameters

• name - name of the Node

Options

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

connect POST requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PostNodeProxy

Parameters

• name - name of the Node

Options

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

connect POST requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PostNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect POST requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PostNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect PUT requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PutNamespacedPodProxy

Parameters

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

Options

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

connect PUT requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PutNamespacedPodProxy

Parameters

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

Options

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

connect PUT requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PutNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect PUT requests to proxy of Pod

OpenAPI Operation ID: connectCoreV1PutNamespacedPodProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Pod
• path - path to the resource

Options

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

connect PUT requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PutNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PUT requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PutNamespacedServiceProxy

Parameters

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

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PUT requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PutNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PUT requests to proxy of Service

OpenAPI Operation ID: connectCoreV1PutNamespacedServiceProxyWithPath

Parameters

• namespace - object name and auth scope, such as for teams and projects
• name - name of the Service
• path - path to the resource

Options

• path - Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.

connect PUT requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PutNodeProxy

Parameters

• name - name of the Node

Options

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

connect PUT requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PutNodeProxy

Parameters

• name - name of the Node

Options

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

connect PUT requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PutNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

connect PUT requests to proxy of Node

OpenAPI Operation ID: connectCoreV1PutNodeProxyWithPath

Parameters

• name - name of the Node
• path - path to the resource

Options

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

create a Namespace

OpenAPI Operation ID: createCoreV1Namespace

Parameters

• body - See Kazan.Apis.Core.V1.Namespace.

Options

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

Response

See Kazan.Apis.Core.V1.Namespace

create a Namespace

OpenAPI Operation ID: createCoreV1Namespace

Parameters

• body - See Kazan.Apis.Core.V1.Namespace.

Options

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

Response

See Kazan.Apis.Core.V1.Namespace

create a Binding

OpenAPI Operation ID: createCoreV1NamespacedBinding

Parameters

• body - See Kazan.Apis.Core.V1.Binding.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Binding

create a Binding

OpenAPI Operation ID: createCoreV1NamespacedBinding

Parameters

• body - See Kazan.Apis.Core.V1.Binding.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Binding

create a ConfigMap

OpenAPI Operation ID: createCoreV1NamespacedConfigMap

Parameters

• body - See Kazan.Apis.Core.V1.ConfigMap.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ConfigMap

create a ConfigMap

OpenAPI Operation ID: createCoreV1NamespacedConfigMap

Parameters

• body - See Kazan.Apis.Core.V1.ConfigMap.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ConfigMap

create Endpoints

OpenAPI Operation ID: createCoreV1NamespacedEndpoints

Parameters

• body - See Kazan.Apis.Core.V1.Endpoints.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Endpoints

create Endpoints

OpenAPI Operation ID: createCoreV1NamespacedEndpoints

Parameters

• body - See Kazan.Apis.Core.V1.Endpoints.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Endpoints

create an Event

OpenAPI Operation ID: createCoreV1NamespacedEvent

Parameters

• body - See Kazan.Apis.Core.V1.Event.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Event

create an Event

OpenAPI Operation ID: createCoreV1NamespacedEvent

Parameters

• body - See Kazan.Apis.Core.V1.Event.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Event

create a LimitRange

OpenAPI Operation ID: createCoreV1NamespacedLimitRange

Parameters

• body - See Kazan.Apis.Core.V1.LimitRange.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.LimitRange

create a LimitRange

OpenAPI Operation ID: createCoreV1NamespacedLimitRange

Parameters

• body - See Kazan.Apis.Core.V1.LimitRange.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.LimitRange

create a PersistentVolumeClaim

OpenAPI Operation ID: createCoreV1NamespacedPersistentVolumeClaim

Parameters

• body - See Kazan.Apis.Core.V1.PersistentVolumeClaim.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.PersistentVolumeClaim

create a PersistentVolumeClaim

OpenAPI Operation ID: createCoreV1NamespacedPersistentVolumeClaim

Parameters

• body - See Kazan.Apis.Core.V1.PersistentVolumeClaim.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.PersistentVolumeClaim

create a Pod

OpenAPI Operation ID: createCoreV1NamespacedPod

Parameters

• body - See Kazan.Apis.Core.V1.Pod.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Pod

create a Pod

OpenAPI Operation ID: createCoreV1NamespacedPod

Parameters

• body - See Kazan.Apis.Core.V1.Pod.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Pod

create binding of a Pod

OpenAPI Operation ID: createCoreV1NamespacedPodBinding

Parameters

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

Options

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

Response

See Kazan.Apis.Core.V1.Binding

create binding of a Pod

OpenAPI Operation ID: createCoreV1NamespacedPodBinding

Parameters

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

Options

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

Response

See Kazan.Apis.Core.V1.Binding

create eviction of a Pod

OpenAPI Operation ID: createCoreV1NamespacedPodEviction

Parameters

• body - See Kazan.Apis.Policy.V1beta1.Eviction.
• namespace - object name and auth scope, such as for teams and projects
• name - name of the Eviction

Options

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

Response

See Kazan.Apis.Policy.V1beta1.Eviction

create eviction of a Pod

OpenAPI Operation ID: createCoreV1NamespacedPodEviction

Parameters

• body - See Kazan.Apis.Policy.V1beta1.Eviction.
• namespace - object name and auth scope, such as for teams and projects
• name - name of the Eviction

Options

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

Response

See Kazan.Apis.Policy.V1beta1.Eviction

create a PodTemplate

OpenAPI Operation ID: createCoreV1NamespacedPodTemplate

Parameters

• body - See Kazan.Apis.Core.V1.PodTemplate.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.PodTemplate

create a PodTemplate

OpenAPI Operation ID: createCoreV1NamespacedPodTemplate

Parameters

• body - See Kazan.Apis.Core.V1.PodTemplate.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.PodTemplate

create a ReplicationController

OpenAPI Operation ID: createCoreV1NamespacedReplicationController

Parameters

• body - See Kazan.Apis.Core.V1.ReplicationController.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ReplicationController

create a ReplicationController

OpenAPI Operation ID: createCoreV1NamespacedReplicationController

Parameters

• body - See Kazan.Apis.Core.V1.ReplicationController.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ReplicationController

create a ResourceQuota

OpenAPI Operation ID: createCoreV1NamespacedResourceQuota

Parameters

• body - See Kazan.Apis.Core.V1.ResourceQuota.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ResourceQuota

create a ResourceQuota

OpenAPI Operation ID: createCoreV1NamespacedResourceQuota

Parameters

• body - See Kazan.Apis.Core.V1.ResourceQuota.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ResourceQuota

create a Secret

OpenAPI Operation ID: createCoreV1NamespacedSecret

Parameters

• body - See Kazan.Apis.Core.V1.Secret.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Secret

create a Secret

OpenAPI Operation ID: createCoreV1NamespacedSecret

Parameters

• body - See Kazan.Apis.Core.V1.Secret.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Secret

create a Service

OpenAPI Operation ID: createCoreV1NamespacedService

Parameters

• body - See Kazan.Apis.Core.V1.Service.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Service

create a Service

OpenAPI Operation ID: createCoreV1NamespacedService

Parameters

• body - See Kazan.Apis.Core.V1.Service.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.Service

create a ServiceAccount

OpenAPI Operation ID: createCoreV1NamespacedServiceAccount

Parameters

• body - See Kazan.Apis.Core.V1.ServiceAccount.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ServiceAccount

create a ServiceAccount

OpenAPI Operation ID: createCoreV1NamespacedServiceAccount

Parameters

• body - See Kazan.Apis.Core.V1.ServiceAccount.
• namespace - object name and auth scope, such as for teams and projects

Options

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

Response

See Kazan.Apis.Core.V1.ServiceAccount

create a Node

OpenAPI Operation ID: createCoreV1Node

Parameters

• body - See Kazan.Apis.Core.V1.Node.

Options

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

Response

See Kazan.Apis.Core.V1.Node

create a Node

OpenAPI Operation ID: createCoreV1Node

Parameters

• body - See Kazan.Apis.Core.V1.Node.

Options

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

Response

See Kazan.Apis.Core.V1.Node

create a PersistentVolume

OpenAPI Operation ID: createCoreV1PersistentVolume

Parameters

• body - See Kazan.Apis.Core.V1.PersistentVolume.

Options

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

Response

See Kazan.Apis.Core.V1.PersistentVolume

create a PersistentVolume

OpenAPI Operation ID: createCoreV1PersistentVolume

Parameters

• body - See Kazan.Apis.Core.V1.PersistentVolume.

Options

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

Response

See Kazan.Apis.Core.V1.PersistentVolume

delete collection of ConfigMap

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedConfigMap

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of ConfigMap

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedConfigMap

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Endpoints

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedEndpoints

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Endpoints

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedEndpoints

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Event

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedEvent

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Event

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedEvent

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of LimitRange

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedLimitRange

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of LimitRange

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedLimitRange

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of PersistentVolumeClaim

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedPersistentVolumeClaim

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of PersistentVolumeClaim

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedPersistentVolumeClaim

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Pod

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedPod

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Pod

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedPod

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of PodTemplate

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedPodTemplate

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of PodTemplate

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedPodTemplate

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of ReplicationController

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedReplicationController

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of ReplicationController

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedReplicationController

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of ResourceQuota

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedResourceQuota

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of ResourceQuota

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedResourceQuota

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Secret

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedSecret

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Secret

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedSecret

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of ServiceAccount

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedServiceAccount

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of ServiceAccount

OpenAPI Operation ID: deleteCoreV1CollectionNamespacedServiceAccount

Parameters

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

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Node

OpenAPI Operation ID: deleteCoreV1CollectionNode

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.

Response

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

delete collection of Node

OpenAPI Operation ID: deleteCoreV1CollectionNode

Options

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

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

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

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

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

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

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

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

• timeout_seconds - Timeout for the list/watch call. 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.