Closed afgane closed 1 year ago
Documenting the discussion here for posterity.
The general helm chart convention is to use appVersion to track the underlying app's version, and to use semantic versioning for the helm chart, so that the two can be independently versioned. Therefore, the key basis for whether the chart needs a major version bump would be whether the chart can be a) Smoothly upgraded without hiccups b) Has no breaking changes to the chart interface Therefore, this particular case would be a minor version bump, despite the major appVersion bump.
We can probably using clamping as a workaround for this: https://total-perspective-vortex.readthedocs.io/en/latest/topics/tpv_by_example.html#clamping-resources In particular, development setups would have to set something like
helm install .... --set jobs.rules.tpv_rules_local\.yml.destinations.k8s.max_cores=2
With https://github.com/galaxyproject/galaxy/pull/15710 that fixes TPV versioning, this is ready for review/merge.
The auto-built image doesn't work out of the box atm because the version of TPV is wrong (see https://github.com/galaxyproject/galaxy/pull/15647#issuecomment-1453926643), but using a manually built image confirms the upgrade is working.
There are two issues/discussion points I'd like to raise: