Skip to content

Commit 0495258

Browse files
committed
Document The WaitForTermination policy
Signed-off-by: Stefan Prodan <[email protected]>
1 parent 98adddb commit 0495258

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/spec/v1/kustomizations.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -181,8 +181,16 @@ Valid values:
181181
`true` and orphaned if `false`.
182182
- `Delete` - Ensure the managed resources are deleted before the Kustomization
183183
is deleted.
184+
- `WaitForTermination` - Ensure the managed resources are deleted and wait for
185+
termination before the Kustomization is deleted.
184186
- `Orphan` - Leave the managed resources when the Kustomization is deleted.
185187

188+
The `WaitForTermination` deletion policy blocks and waits for the managed
189+
resources to be removed from etcd by the Kubernetes garbage collector.
190+
The wait time is determined by the `.spec.timeout` field. If a timeout occurs,
191+
the controller will log an error and will allow the Kustomization to be
192+
deleted while the managed resources will be left in the cluster.
193+
186194
For special cases when the managed resources are removed by other means (e.g.
187195
the deletion of the namespace specified with
188196
[`.spec.targetNamespace`](#target-namespace)), you can set the deletion policy

0 commit comments

Comments
 (0)