fix: remove pod finalizer in abnormal scenarios #15164
Open
+4
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We enabled the finalizer feature in our production environment (20,000 workflows), but encountered two online issues: 1. When a pending pod is deleted by another service, it gets stuck in the
Terminatingstate, waiting for the finalizer to be cleaned up., however, the PodDeleteFuncdoesn't receive the deletion event; in fact, theUpdateFuncreceives the update event, causing the Pod Finalizer to fail to clean up. 2. When the workflow controller restarts, the PodAddFuncreceives historical creation events and cannot clean up the finalizer.Modifications
Regardless of the event detected in the Pod, the system will determine whether the Pod has been deleted based on the Pod
DeletionTimestampfield and delete the Finalizer accordingly.deleting := pod.DeletionTimestamp != nil c.commonPodEvent(ctx, pod, deleting)Doucument
Like this, when pod is cleaned up by other services,
DeletionTimestampis set, this is the Update event.