Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with drift detection with upgrade.force=true #803

Closed
rsafonseca opened this issue Nov 9, 2023 · 1 comment
Closed

Issue with drift detection with upgrade.force=true #803

rsafonseca opened this issue Nov 9, 2023 · 1 comment

Comments

@rsafonseca
Copy link

Drift detection only detects drift when the fields managed by the helm-controller are changed.
A user can add additional fields and drift detection will ignore them and won't roll them back.

When upgrade.force=true is set, the replacement strategy is used an all fields not managed by the helm-controller are lost.

This causes an inconsistency in the expected behaviour and can lead to some fields being dropped at an unexpected time after a helmrelease upgrade is triggered.

@stefanprodan
Copy link
Member

Fixed by: #822

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

No branches or pull requests

2 participants