feat: expose Force on PolicyRef/KustomizationRef to recover from rejected updates#1877
Merged
Merged
Conversation
gianlucam76
force-pushed
the
yaml-force
branch
2 times, most recently
from
July 17, 2026 05:43
eeabd73 to
47defdc
Compare
…cted updates libsveltos' `deployer.UpdateResource` now supports a `forceRecreate` option: when an apply is rejected with an error that only a delete+recreate can fix (eg a Deployment moving to `strategy.type: Recreate` while the API server's previously-defaulted `rollingUpdate` is still set), the object is deleted and recreated instead of surfacing the error. This wires that option up to `PolicyRef.Force` and `KustomizationRef.Force`
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
libsveltos'
deployer.UpdateResourcenow supports aforceRecreateoption: when an apply is rejected with an error that only a delete+recreate can fix (eg a Deployment moving tostrategy.type: Recreatewhile the API server's previously-defaultedrollingUpdateis still set), the object is deleted and recreated instead of surfacing the error. This wires that option up toPolicyRef.ForceandKustomizationRef.Force