Skip to content

Commit 34bc383

Browse files
committed
Updating Finalizers information with a note
1 parent ccca5c2 commit 34bc383

File tree

1 file changed

+8
-1
lines changed
  • content/en/docs/concepts/overview/working-with-objects

1 file changed

+8
-1
lines changed

content/en/docs/concepts/overview/working-with-objects/finalizers.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ and does the following:
2626

2727
* Modifies the object to add a `metadata.deletionTimestamp` field with the
2828
time you started the deletion.
29-
* Prevents the object from being removed until its `metadata.finalizers` field is empty.
29+
* Prevents the object from being removed until its `metadata.finalizers` field is removed as `finalizers` can not be added or changed.
3030
* Returns a `202` status code (HTTP "Accepted")
3131

3232
The controller managing that finalizer notices the update to the object setting the
@@ -45,6 +45,13 @@ controller can't delete it because the finalizer exists. When the Pod stops
4545
using the `PersistentVolume`, Kubernetes clears the `pv-protection` finalizer,
4646
and the controller deletes the volume.
4747

48+
{{<note>}}
49+
* When you `DELETE` an object, Kubernetes makes that object almost read-only with exception that the
50+
`metadata.deletionTimestamp` field gets set and the `finalizers` can be removed. Thus `deletionTimestamp` is immutable.
51+
52+
* After the deletion is requested, you can not resurrect this object. The only way is to delete it and make a new similar object.
53+
{{</note>}}
54+
4855
## Owner references, labels, and finalizers {#owners-labels-finalizers}
4956

5057
Like {{<glossary_tooltip text="labels" term_id="label">}},

0 commit comments

Comments
 (0)