Open RolandWolman opened 9 months ago
"Charts bitnami/postgresql:12.5.6 and bitnami/redis:17.17.1 are using incompatible versions of bitnami/common. The issue can be fixed by updating the bitnami/postgresql chart to a version later than 12.9.0.
Edit: Version 2.9.0 of bitnami/common was indeed backward-compatible (https://github.com/bitnami/charts/pull/18154). The issue appears to be with Helm handling conflicting dependencies.
In this case, redis:18.2.0 uses bitnami/common:2.13.3, while postgresql:12.5.6 uses bitnami/common:2.8.0. IMO, expected behavior should be that Helm should prioritise bitnami/common:2.13.3 over 2.8.0, because it is the latest under the same major." taken from https://github.com/bitnami/charts/issues/20504
Hi @nmanovic This issue is due to unmatched versions of common sub charts in Postgres, Redis. I have separately installed common chart as sub dependency, and tested. I have faced no issues then. Please assign this issue to me.
Actions before raising this issue
Steps to Reproduce
values.yaml
containingand the default versions from
Chart.yaml
helm upgrade --install
results in
Error: UPGRADE FAILED: template: cvat/charts/redis/templates/master/service.yaml:12:14: executing "cvat/charts/redis/templates/master/service.yaml" at <include "common.labels.standard" (dict "customLabels" .Values.commonLabels "context" $)>: error calling include: template: cvat/charts/postgresql/charts/common/templates/_labels.tpl:6:27: executing "common.labels.standard" at <include "common.names.name" .>: error calling include: template: cvat/charts/postgresql/charts/common/templates/_names.tpl:6:18: executing "common.names.name" at <.Chart.Name>: nil pointer evaluating interface {}.Name
Chart.lock
Expected Behavior
Helm installation should run successfully
Possible Solution
upgrade postgres version in Chart.yaml
as suggest in this issue resolves the issue.
Chart.lock
now looks like thisfor the redis
Chart.lock
we getand postgres
Chart.lock
These versions of common seem to be more compatible.
Context
No response
Environment
No response