By separating helm chart updates from helm values updates we can still have automatic updates for container images regardless of changes carried by the helm charts.
By example instead of getting one PR like https://github.com/timescale/tobs/pull/515 which updates container images and otel-operator helm chart, we should get 2 PRs - one for image updates and one for otel-operator helm chart. This in turn allows us to still update images regardless of issues with otel-operator helm chart.
Type of change
What type of changes does your code introduce to tobs? Put an x in the box that apply.
[ ] CHANGE (fix or feature that would cause existing functionality to not work as expected)
[ ] FEATURE (non-breaking change which adds functionality)
[ ] BUGFIX (non-breaking change which fixes an issue)
[ ] ENHANCEMENT (non-breaking change which improves existing functionality)
[x] NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)
Description
By separating helm chart updates from helm values updates we can still have automatic updates for container images regardless of changes carried by the helm charts.
By example instead of getting one PR like https://github.com/timescale/tobs/pull/515 which updates container images and otel-operator helm chart, we should get 2 PRs - one for image updates and one for otel-operator helm chart. This in turn allows us to still update images regardless of issues with otel-operator helm chart.
Type of change
What type of changes does your code introduce to tobs? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)