Two week’s ago, Temporal’s Helm Charts (https://github.com/temporalio/helm-charts) reached the important 1.0.0 milestone. This has been a community effort — nearly 150 contributors, two-thirds of them from outside Temporal. Thanks to everyone who filed issues, submitted PRs, and helped others along the way.
If you’ve been using an older version, please be aware of important changes described in the repo’s UPGRADING.md file. For a summary of the changes, you can also check out this blog post.
BTW, the 1.0.0 release was a milestone, not the end of the road, and there have been two more releases of the Helm Charts since then.
2 Likes
Thanks for the update, and congrats on the 1.0+ milestone.
We’re currently on the older Temporal Helm chart (0.73.1, server 1.29.1) and are evaluating migration to the newer 1.x line. One question we’re trying to clarify: with the new raw persistence config in 1.x, is there now any supported way for MySQL persistence to use either:
-
a comma-separated multi-host connectAddr, or
-
an SRV-backed DNS name for failover/discovery
for cases where MySQL is a 3-node setup but there is no single LB/VIP endpoint available?
From reading the current chart/templates and Temporal server MySQL code, it still looks like the chart now passes connectAddr through more directly, but the server runtime still expects a single effective MySQL address rather than native host-list or SRV failover.
Happy to open a separate issue/forum thread if that’s better.
As you’ve noted Temporal server does not support a comma separated connectAddr, so this would not work currently. You’d need to file an issue against Temporal server.
Once implemented I think the chart would then do the right thing, as we already have code to support comma-separation chart side as our Postgres PGX adapter supports it.