英文:
Cancel deletion of a Kubernetes Resource from Finalizer
问题
在Kubernetes中，有一个deletionTimestamp用于表示正在进行的删除操作，还有finalizers用于在删除过程中建模任务。
然而，在删除过程中，可能会出现父对象规范发生变化的情况，这将使取消删除成为最理想的解决方案。
我期望有一个清晰而完整的文档，涵盖了deletionTimestamp和finalization在整个删除过程中的生命周期。似乎大多数人都认为它要么是零，要么是非零，并且在非零时不能更改。然而，似乎没有关于此的文档。我也不想“只是检查”，因为“只是检查”可能会发生变化，明天可能就无法工作了。
英文:
In Kubernetes, there is deletionTimestamp to signal an ongoing deletion and there are finalizers to model tasks during the process of deletion.
However, it could be, that during the deletion, the specification of a parent object changes in a way that would effective make cancelling the deletion the most desirable solution.
I'd expect a clear and complete documentation of deletionTimestamp and finalization covering the entire lifecycle of deletionTimestamp. It seems that most people seem to assume that it is either zero or nonzero and cannot be changed while it is nonzero. However, there seems to be no documentation on that. I also do not want to "just check", because just check is subject to change and may stop working tomorrow.
答案1
得分: 1
答案是否定的，
Finalizers是命名空间键，告诉Kubernetes在完全删除标记为删除的资源之前等待特定条件满足。Finalizers会通知控制器清理已删除对象所拥有的资源。文档在这里。
原因是垃圾回收使用了这个标识符，在前台级联删除中，您要删除的所有者对象首先进入正在进行删除的状态。详细了解请阅读前台级联删除。
英文:
The answer is No,
Finalizers are namespaced keys that tell Kubernetes to wait until specific conditions are met before it fully deletes resources marked for deletion. Finalizers alert controllers to clean up resources the deleted object owned. Documentation is here
Reason being garbage collection used this identifier, In foreground cascading deletion, the owner object you're deleting first enters a deletion in progress state Read through this for detailed understanding
Foreground cascading deletion
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论