New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helm chart version control #11320
Comments
We have other versions before, likes 1.0.0, but we deletes these versions because we deprecated some Bytebase images.
Oops, it seems like we forget to bump the Helm version while we add support for resource control via #11094.
We will look into this, thanks! |
Thanks for your answer, how to bump the Helm version? Maybe change this Chart.yaml. We use argocd to dependencies a version of Helm. If the version is deprecated, there may be a dependencies failure? |
Yes, but we do not bump the helm (package?) version while we release new version of Bytebase, unless we adjust the chart to support new features or new options. Otherwise, we just upgrade the bytebase version value in the chart.
Maybe. I am not familiar with argocd, but the deprecate operation is very rare and should not be a concern. We delete the old charts because of they reference the deprecated Bytebase images. Otherwise, we would receive numerous artifact hub alert emails which say "Cannot find image." |
Is it a good practice to bump the helm package version if we modify the default value in values.yaml? |
Maybe every change is a new chart version. |
There are example, like kube-prometheus-stack and grafana, have a helm-chart repository, contains many versions of charts. usage document. |
appVersion is usually the bytebase docker image version. |
Is your feature request related to a problem?
The bytebase helm chart version is always 1.1.0. When new features are added in the chart, it is still this version. There is no way to helm upgrade?
Describe the solution you'd like
Additional context
No response
The text was updated successfully, but these errors were encountered: