Skip to main content
Upgrade 12.0.0 and 12.0.1 hubs straight to hub chart 12.0.2. The patch releases fix two problems:
  • 12.0.1: Temporal failing to start on hubs with bundled PostgreSQL (details below).
  • 12.0.2: Guardian chat failing with “Sorry, I encountered an error while processing your request.” on hubs served over plain HTTP. Browsers only provide the crypto.randomUUID API on HTTPS pages, and the Guardian UI relied on it. The fix is in the onprem-12.0.2 apiserver image; the other application images are byte-identical to 12.0.0.
The exporter chart stays at 12.0.0, so monitored clusters need no upgrade.

PostgreSQL connections (12.0.1)

On 12.0.0 the bundled PostgreSQL kept its default max_connections of 100. Temporal’s 12 server pods hold up to 20 pooled connections each on the temporal database plus their visibility pools, so the last Temporal pods to start never got a connection and crashlooped with no usable database connection found. Alerts, CRD sync and Guardian workflows depend on Temporal. 12.0.1 and later:
  • raise the bundled PostgreSQL max_connections to 400 through the new postgres.bundled.cluster.parameters value, and
  • size the Temporal pools explicitly: 20 connections for the default store and 5 for visibility per pod, a worst case of 300 with the default replica counts.
If you raise Temporal replica counts or pool sizes, raise postgres.bundled.cluster.parameters.max_connections to match. If you use external PostgreSQL, make sure it allows at least 400 connections for Metoro.
Hub commands assume the Helm release is named metoro and runs in the metoro-hub namespace. Adjust them if your installation uses different values.

Upgrade The Hub

Start from the values file used for the existing hub release. If you do not have it locally, export the user-supplied Helm values:
Upgrade the hub chart to 12.0.2:
If you worked around 12.0.0 by editing the metoro-postgresql Cluster directly (for example kubectl patch ... max_connections) and you run Helm 4, the upgrade fails with conflict with "kubectl-patch" ... .spec.postgresql.parameters.max_connections, because Helm 4 applies changes server-side and that field now has another owner. Re-run the same helm upgrade command with --force-conflicts so the chart takes ownership of the value. Helm 3 is not affected.
The PostgreSQL operator applies the new max_connections with a rolling restart of the PostgreSQL instances, including a switchover of the primary. Wait for it to finish, then restart Temporal so any crashlooping pods reconnect immediately:

Check The Rollout

Expected outcome:
  • The metoro-postgresql cluster reports Cluster in healthy state and SHOW max_connections returns 400.
  • Every Temporal pod is Running and ready.
  • Existing PostgreSQL, ClickHouse, Temporal, and telemetry data remain in place.