You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm addressing an issue where the default helm-values manager of Renovate fails to recognize the custom image options in the k8s-operator chart's values file. It expects repository, but it's repo in this chart (docs).
How should we solve this?
Renaming is a simple but breaking change. A backward-compatible option would be supporting both names, but it adds unnecessary complexity.
What is the impact of not solving this?
Currently, using Renovate with this chart requires a custom manager, detailed here. This needs to be done for each Renovate instance supporting this chart.
The text was updated successfully, but these errors were encountered:
Yeradon
changed the title
FR: Update custom operator image configuration for Renovate compatibility
FR: Update k8s-operator custom image configuration for Renovate compatibility
May 11, 2024
A backward-compatible option would be supporting both names, but it adds unnecessary complexity
We should not break existing users. If this can be done in a backwards compatible manner, happy for this to be added. Helm syntax should support picking one of two values for a template field, depening on which is set if any.
What are you trying to do?
I'm addressing an issue where the default helm-values manager of Renovate fails to recognize the custom image options in the k8s-operator chart's values file. It expects
repository
, but it'srepo
in this chart (docs).How should we solve this?
Renaming is a simple but breaking change. A backward-compatible option would be supporting both names, but it adds unnecessary complexity.
What is the impact of not solving this?
Currently, using Renovate with this chart requires a custom manager, detailed here. This needs to be done for each Renovate instance supporting this chart.
The text was updated successfully, but these errors were encountered: