Skip to content

[eno] Add cross-reconciler deletion ordering fix#571

Open
ruinan-liu wants to merge 4 commits intomainfrom
users/ruinanliu/foreground-deletion-fix
Open

[eno] Add cross-reconciler deletion ordering fix#571
ruinan-liu wants to merge 4 commits intomainfrom
users/ruinanliu/foreground-deletion-fix

Conversation

@ruinan-liu
Copy link
Contributor

No description provided.

logger.Info("FailOpen - suppressing errors")
err = nil
modified = false
if snap == nil || (!snap.ForegroundDeletion && !resource.HasDeletionGroup()) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it is ForgroundDeletion or has deletion group, we don't ignore the reconciliation. Does it sound a behavior change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this would be a behavior change.

Our previous fail-open logic was broad and prioritized liveness, making deletion ordering more of a best-effort guarantee. However, ForegroundDeletion and DeletionGroup imply a stricter contract. In those cases, failing open would weaken the intended ordering guarantees.

I don't think we are moving away from deletion faillingOpen globally, but we need to make sure the deletion ordering is respected fully?

// Don't fail open for resources with deletion ordering contraints -
// suppressing errors would break deletion group/ foreground deletion ordering
if failingOpen && snap != nil && (snap.ForegroundDeletion || resource.HasDeletionGroup()) {
failingOpen = false
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to do it at line 157?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, thanks

@ruinan-liu ruinan-liu marked this pull request as ready for review February 25, 2026 17:10
Copy link
Contributor Author

@ruinan-liu ruinan-liu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Respond to comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants