Skip to content

Conversation

@patchback
Copy link

@patchback patchback bot commented Apr 28, 2025

This is a backport of PR #802 as merged into main (00699ac).

SUMMARY

Starting with version 3.14.0, Helm supports --reset-then-reuse-values. As discussed on the original PR. This greatly improves on --reuse-values as it allows to avoid templates errors when new features are added to an upgraded chart.

Closes #803

ISSUE TYPE
  • Feature Pull Request
COMPONENT NAME

helm

ADDITIONAL INFORMATION

This PR is greatly 'inspired' by #575 and because I wasn't sure how I could provide additional tests for it, I actually copied those build previously for --reuse-values (as it is an improvement on this feature.

SUMMARY
Starting with version 3.14.0, Helm supports --reset-then-reuse-values. As discussed on the original PR. This greatly improves on --reuse-values as it allows to avoid templates errors when new features are added to an upgraded chart.
Closes #803
ISSUE TYPE

Feature Pull Request

COMPONENT NAME
helm
ADDITIONAL INFORMATION
This PR is greatly 'inspired' by #575 and because I wasn't sure how I could provide additional tests for it, I actually copied those build previously for --reuse-values (as it is an improvement on this feature.

Reviewed-by: Bikouo Aubin
Reviewed-by: Yuriy Novostavskiy
Reviewed-by: b0z02003
Reviewed-by: Bianca Henderson <[email protected]>
(cherry picked from commit 00699ac)
@softwarefactory-project-zuul
Copy link

@yurnov
Copy link
Contributor

yurnov commented Apr 28, 2025

Probably we should backport that chnage to stable-5, but I'm not sure that is reasonable do it for stable-3.

Idea that new features will go to 5.x.y and 6.x.y, and only bugfixes to 3.x.y. Let it discuss separately.

@beeankha
Copy link
Contributor

Probably we should backport that chnage to stable-5, but I'm not sure that is reasonable do it for stable-3.

Idea that new features will go to 5.x.y and 6.x.y, and only bugfixes to 3.x.y. Let it discuss separately.

That makes sense, @yurnov . I am going to go ahead and close this backport PR.

@beeankha beeankha closed this Apr 29, 2025
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.

4 participants