version conventions #615
Unanswered
justinrixx
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
hi there,
i'm looking for guidance as to what sorts of conventions are followed for new versions of the helm charts. i've noticed all of the recent releases seem to have a bare description, minus the same boilerplate text, and i don't see any guidance documented anywhere regarding upgrading the helm chart.
specifically, i'm looking for how the helm chart versions should interact with versions of temporal itself. i'm able to override the temporal version in the helm values by setting
server.image.tag
. is this a bad idea? how often does the helm chart release with features to support new changes in temporal server? temporal server has documented guarantees around minor version drift vs database schema; is there a similar expectation for the helm charts? or am i better off holding off upgrading to a new temporal server version until the new version is reflected in a new release of the helm chart?Beta Was this translation helpful? Give feedback.
All reactions