Skip to content

Conversation

@johnksv
Copy link
Contributor

@johnksv johnksv commented Jan 9, 2026

the force-conflicts flag to start with. This is because of the breaking change in helm 3 -> helm 4, where helm 4 will fail without this flag when a field is managed by another entity then helm.

The implementation allows one to easily add helm flags on the region - which will then be used during helm upgrade (i.e. install, suspend, resume). The reason to add it on the region is that these flags make sense for all services rather then on a catalog or service level (these kind of flags manipulate how helm functions, and we want the same result for all services, at least as of now).

…start with

The implementation allows one to easily add helm flags on the region - which will then be used during helm upgrade (i.e. install, suspend, resume).
The reason to add it on the region is that these flags make sense for all services rather then on a catalog or service level (these kind of flags manipulate how helm functions, and we want the same result for all services, at least as of now).
@fcomte fcomte requested a review from olevitt January 9, 2026 13:39
forceConflicts requires that upgrade is done server side. Thus we want the ability to supply this flag
@sonarqubecloud
Copy link

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.

1 participant