Server.config.archival values not applied to config_template.yaml when using Temporal Helm chart 0.71.0

Community Support
1

I’m deploying Temporal

1.29.0

using the official Helm chart

0.71.0

on GKE with GCS archival. I’ve configured archival in my Helm values under

server.config.archival

but the rendered

config_template.yaml

inside the pod always shows:

archival:
status: “disabled”

regardless of what I set in values.

My Helm values (

server.config.archival

section):

server:
config:
archival:
history:
state: “enabled”
enableRead: true
provider:
gstorage:
default:
credentialsPath: “”
visibility:
state: “enabled”
enableRead: true
provider:
gstorage:
default:
credentialsPath: “”
namespaceDefaults:
archival:
history:
state: “enabled”
URI: “gs://my-history-bucket”
visibility:
state: “enabled”
URI: “gs://my-visibility-bucket”

What I’ve tried:

  • Setting

    server.archival

    (outside

    config

    ) — same result

  • Enabling via

    temporal operator namespace update

    CLI — succeeds but namespace still shows

    HistoryArchivalState: Disabled

  • Verified GCS buckets exist and Helm chart redeployed

Questions:

  1. What is the correct Helm values path to enable archival in chart

    0.71.0

    ?

  2. Does the chart support GCS archival config injection or does it require a manual

    ConfigMap

    patch?

  3. Is

    server.config.archival

    the correct key or is there a different path?

Environment:

  • Temporal server:

    1.29.0

  • Helm chart:

    0.71.0

  • Persistence: PostgreSQL

  • Archival provider: GCS (

    gstorage

    )

  • Platform: GKE with Workload Identity

3

can anyone please help to fix the issue.