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
First of all, thanks for providing and maintaining this Helm chart!
I would be nice if the Helm chart was automatically tracking the latest (stable) release of langfuse via bumps to the appVersion.
Currently it seems to use a major appVersion of "2" .
while this is nice to always start with most recent version 2.x.y, this is not as explicit as one would like.
Event though you have the imagePullPolicy set to always, this requires the recreation of the Pod which then does not happen explicitly via a helm upgrade but co-incidentally with other K8s cluster operations.
I'd rather just use the Helm chart version as the "package version" and as an indicator that there is an update available.
The text was updated successfully, but these errors were encountered:
First of all, thanks for providing and maintaining this Helm chart!
I would be nice if the Helm chart was automatically tracking the latest (stable) release of langfuse via bumps to the
appVersion
.Currently it seems to use a major
appVersion
of "2" .while this is nice to always start with most recent version 2.x.y, this is not as explicit as one would like.
Event though you have the
imagePullPolicy
set to always, this requires the recreation of the Pod which then does not happen explicitly via ahelm upgrade
but co-incidentally with other K8s cluster operations.I'd rather just use the Helm chart version as the "package version" and as an indicator that there is an update available.
The text was updated successfully, but these errors were encountered: