OPENSHIFT KUBE(1)

NAME

openshift kube delete - Delete resources by filenames, stdin, resources and names, or by resources and label selector

SYNOPSIS

openshift kube delete [OPTIONS]

DESCRIPTION

Delete resources by filenames, stdin, resources and names, or by resources and label selector.

JSON and YAML formats are accepted. Only one type of the arguments may be specified: filenames, resources and names, or resources and label selector.

Some resources, such as pods, support graceful deletion. These resources define a default period before they are forcibly terminated (the grace period) but you may override that value with the --grace-period flag, or pass --now to set a grace-period of 1. Because these resources often represent entities in the cluster, deletion may not be acknowledged immediately. If the node hosting a pod is down or cannot reach the API server, termination may take significantly longer than the grace period. To force delete a resource, you must pass a grace period of 0 and specify the --force flag.

IMPORTANT: Force deleting pods does not wait for confirmation that the pod's processes have been terminated, which can leave those processes running until the node detects the deletion and completes graceful deletion. If your processes use shared storage or talk to a remote API and depend on the name of the pod to identify themselves, force deleting those pods may result in multiple processes running on different machines using the same identification which may lead to data corruption or inconsistency. Only force delete pods when you are sure the pod is terminated, or if your application can tolerate multiple copies of the same pod running at once. Also, if you force delete pods the scheduler may place new pods on those nodes before the node has released those resources and causing those pods to be evicted immediately.

Note that the delete command does NOT do resource version checks, so if someone submits an update to a resource right when you submit a delete, their update will be lost along with the rest of the resource.

OPTIONS

--all=false
    [-all] to select all the specified resources.

--cascade=true
    If true, cascade the deletion of the resources managed by this resource (e.g. Pods created by a ReplicationController). Default true.

-f, --filename=[]
    Filename, directory, or URL to files containing the resource to delete.

--force=false
    Immediate deletion of some resources may result in inconsistency or data loss and requires confirmation.

--grace-period=-1
    Period of time in seconds given to the resource to terminate gracefully. Ignored if negative.

--ignore-not-found=false
    Treat "resource not found" as a successful delete. Defaults to "true" when --all is specified.

--include-extended-apis=true
    If true, include definitions of new APIs via calls to the API server. [default true]

--now=false
    If true, resources are signaled for immediate shutdown (same as --grace-period=1).

-o, --output=""
    Output mode. Use "-o name" for shorter output (resource/name).

-R, --recursive=false
    Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.

-l, --selector=""
    Selector (label query) to filter on.

--timeout=0
    The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object

OPTIONS INHERITED FROM PARENT COMMANDS

--allow-verification-with-non-compliant-keys=false
    Allow a SignatureVerifier to use keys which are technically non-compliant with RFC6962.

--alsologtostderr=false
    log to standard error as well as files

--api-version=""
    DEPRECATED: The API version to use when talking to the server

--application-metrics-count-limit=100
    Max number of application metrics to store (per container)

--as=""
    Username to impersonate for the operation

--azure-container-registry-config=""
    Path to the file container Azure container registry configuration information.

--boot-id-file="/proc/sys/kernel/random/boot_id"
    Comma-separated list of files to check for boot-id. Use the first one that exists.

--certificate-authority=""
    Path to a cert. file for the certificate authority

--client-certificate=""
    Path to a client certificate file for TLS

--client-key=""
    Path to a client key file for TLS

--cluster=""
    The name of the kubeconfig cluster to use

--config=""
    Path to the config file to use for CLI requests.

--container-hints="/etc/cadvisor/container_hints.json"
    location of the container hints file

--context=""
    The name of the kubeconfig context to use

--docker="unix:///var/run/docker.sock"
    docker endpoint

--docker-env-metadata-whitelist=""
    a comma-separated list of environment variable keys that needs to be collected for docker containers

--docker-only=false
    Only report docker containers in addition to root stats

--docker-root="/var/lib/docker"
    DEPRECATED: docker root is read from docker info (this is a fallback, default: /var/lib/docker)

--enable-load-reader=false
    Whether to enable cpu load reader

--event-storage-age-limit="default=0"
    Max length of time for which to store events (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is a duration. Default is applied to all non-specified event types

--event-storage-event-limit="default=0"
    Max number of events to store (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is an integer. Default is applied to all non-specified event types

--global-housekeeping-interval=0
    Interval between global housekeepings

--google-json-key=""
    The Google Cloud Platform Service Account JSON Key to use for authentication.

--housekeeping-interval=0
    Interval between container housekeepings

--httptest.serve=""
    if non-empty, httptest.NewServer serves on this address and blocks

--insecure-skip-tls-verify=false
    If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure

--ir-data-source="influxdb"
    Data source used by InitialResources. Supported options: influxdb, gcm.

--ir-dbname="k8s"
    InfluxDB database name which contains metrics required by InitialResources

--ir-hawkular=""
    Hawkular configuration URL

--ir-influxdb-host="localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb:api"
    Address of InfluxDB which contains metrics required by InitialResources

--ir-namespace-only=false
    Whether the estimation should be made only based on data from the same namespace.

--ir-password="root"
    Password used for connecting to InfluxDB

--ir-percentile=90
    Which percentile of samples should InitialResources use when estimating resources. For experiment purposes.

--ir-user="root"
    User used for connecting to InfluxDB

--kubeconfig=""
    Specify a kubeconfig file to define the configuration

--log-backtrace-at=:0
    when logging hits line file:N, emit a stack trace

--log-cadvisor-usage=false
    Whether to log the usage of the cAdvisor container

--log-dir=""
    If non-empty, write log files in this directory

--log-flush-frequency=0
    Maximum number of seconds between log flushes

--logtostderr=true
    log to standard error instead of files

--machine-id-file="/etc/machine-id,/var/lib/dbus/machine-id"
    Comma-separated list of files to check for machine-id. Use the first one that exists.

--match-server-version=false
    Require server version to match client version

-n, --namespace=""
    If present, the namespace scope for this CLI request

--request-timeout="0"
    The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.

--server=""
    The address and port of the Kubernetes API server

--stderrthreshold=2
    logs at or above this threshold go to stderr

--storage-driver-buffer-duration=0
    Writes in the storage driver will be buffered for this duration, and committed to the non memory backends as a single transaction

--storage-driver-db="cadvisor"
    database name

--storage-driver-host="localhost:8086"
    database host:port

--storage-driver-password="root"
    database password

--storage-driver-secure=false
    use secure connection with database

--storage-driver-table="stats"
    table name

--storage-driver-user="root"
    database username

--token=""
    Bearer token for authentication to the API server

--user=""
    The name of the kubeconfig user to use

-v, --v=0
    log level for V logs

--vmodule=
    comma-separated list of pattern=N settings for file-filtered logging

EXAMPLE

      # Delete a pod using the type and name specified in pod.json.
      kubectl delete -f ./pod.json

      # Delete a pod based on the type and name in the JSON passed into stdin.
      cat pod.json | kubectl delete -f -

      # Delete pods and services with same names "baz" and "foo"
      kubectl delete pod,service baz foo

      # Delete pods and services with label name=myLabel.
      kubectl delete pods,services -l name=myLabel

      # Delete a pod with minimal delay
      kubectl delete pod foo --now

      # Force delete a pod on a dead node
      kubectl delete pod foo --grace-period=0 --force

      # Delete a pod with UID 1234-56-7890-234234-456456.
      kubectl delete pod 1234-56-7890-234234-456456

      # Delete all pods
      kubectl delete pods --all

SEE ALSO

openshift-kube(1),

HISTORY

June 2016, Ported from the Kubernetes man-doc generator