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
{{ message }}
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.
@billimek how do you feel if we remove this field from the Chart.yaml? It seems like the field is useless for a bunch of applications that do not require a chart update when a image is updated.
My line of thinking is that the command helm list --all-namespaces -a, or the helm-exporter is not returning the correct appVersion if we update the image. That makes this metadata wrong.
Of-course the proper way to handle this is to release a new chart version on every image update, but we don't really have the time to do that since new versions get released all the time, almost daily.
The text was updated successfully, but these errors were encountered:
onedr0p
changed the title
appVersion in Chart.yaml
Remove appVersion in Chart.yaml
Apr 8, 2020
This essentially ties the image tag to the AppVersion in Chart.yaml which I think would break automation like flux. So I personally don't care for that approach.
It does seem like appVersion is extraneous. Is it a required field?
@billimek how do you feel if we remove this field from the Chart.yaml? It seems like the field is useless for a bunch of applications that do not require a chart update when a image is updated.
My line of thinking is that the command
helm list --all-namespaces -a
, or the helm-exporter is not returning the correct appVersion if we update the image. That makes this metadata wrong.Of-course the proper way to handle this is to release a new chart version on every image update, but we don't really have the time to do that since new versions get released all the time, almost daily.
The text was updated successfully, but these errors were encountered: