1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
use ArgPredicate;
use *;
/// Delete resources by file names, stdin, resources and names, or by resources and label selector.
// JSON and YAML formats are accepted. Only one type of argument may be specified: file names, 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 specify the --force flag. Note: only a
// subset of resources support graceful deletion. In absence of the support, the --grace-period flag is ignored.
// 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.
// After a CustomResourceDefinition is deleted, invalidation of discovery cache may take up to 6 hours. If you don't want
// to wait, you might want to run "kubectl api-resources" to refresh the discovery cache.
// Examples:
// # Delete a pod using the type and name specified in pod.json
// kubectl delete -f ./pod.json
// # Delete resources from a directory containing kustomization.yaml - e.g. dir/kustomization.yaml
// kubectl delete -k dir
// # Delete resources from all files that end with '.json'
// kubectl delete -f '*.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 --force
// # Delete all pods
// kubectl delete pods --all
// # Delete all pods only if the user confirms the deletion
// kubectl delete pods --all --interactive
// Options:
// --all=false:
// Delete all resources, in the namespace of the specified resource types.
// -A, --all-namespaces=false:
// If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even
// if specified with --namespace.
// --cascade='background':
// Must be "background", "orphan", or "foreground". Selects the deletion cascading strategy for the dependents
// (e.g. Pods created by a ReplicationController). Defaults to background.
// --dry-run='none':
// Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without
// sending it. If server strategy, submit server-side request without persisting the resource.
// --field-selector='':
// Selector (field query) to filter on, supports '=', '==', and '!='.(e.g. --field-selector
// key1=value1,key2=value2). The server only supports a limited number of field queries per type.
// -f, --filename=[]:
// containing the resource to delete.
// --force=false:
// If true, immediately remove resources from API and bypass graceful deletion. Note that 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. Set to 1 for
// immediate shutdown. Can only be set to 0 when --force is true (force deletion).
// --ignore-not-found=false:
// Treat "resource not found" as a successful delete. Defaults to "true" when --all is specified.
// -i, --interactive=false:
// If true, delete resource only when user confirms.
// -k, --kustomize='':
// Process a kustomization directory. This flag can't be used together with -f or -R.
// --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).
// --raw='':
// Raw URI to DELETE to the server. Uses the transport specified by the kubeconfig file.
// -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, supports '=', '==', '!=', 'in', 'notin'.(e.g. -l
// key1=value1,key2=value2,key3 in (value3)). Matching objects must satisfy all of the specified label
// constraints.
// --timeout=0s:
// The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the
// object
// --wait=true:
// If true, wait for resources to be gone before returning. This waits for finalizers.
// Usage:
// kubectl delete ([-f FILENAME] | [-k DIRECTORY] | TYPE [(NAME | -l label | --all)]) [options]
// Use "kubectl options" for a list of global command-line options (applies to all commands).