OC(1)

NAME

oc delete - Delete one or more resources

SYNOPSIS

oc delete [OPTIONS]

DESCRIPTION

Delete a resource

JSON and YAML formats are accepted.

If both a filename and command line arguments are passed, the command line arguments are used and the filename is ignored.

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 a file containing the resource to delete.

--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 force terminated without graceful deletion (same as --grace-period=0).

-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

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

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

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

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

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

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

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

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

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

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

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

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

EXAMPLE

      # Delete a pod using the type and ID specified in pod.json.
      oc delete -f pod.json
      # Delete a pod based on the type and ID in the JSON passed into stdin.
      cat pod.json | oc delete -f -
      # Delete pods and services with label name=myLabel.
      oc delete pods,services -l name=myLabel
      # Delete a pod with name node-1-vsjnm.
      oc delete pod node-1-vsjnm
      # Delete all resources associated with a running app, includes
      # buildconfig,deploymentconfig,service,imagestream,route and pod,
      # where 'appName' is listed in 'Labels' of 'oc describe [resource] [resource name]' output.
      oc delete all -l app=appName
      # Delete all pods
      oc delete pods --all

SEE ALSO

oc(1),

HISTORY

June 2016, Ported from the Kubernetes man-doc generator