[Bug] Helm chart does not expose configuration for secondaryVisibilityStore (Dual ES Visibility)

[ignaciogonzalezsomoza]

What are you really trying to do?

I’m trying to configure Temporal Server (v1.29.0) to use dual visibility stores (Elasticsearch + Elasticsearch). Temporal’s server code (persistence.go) supports multiple visibility stores of the same type, and I want to enable this through the Helm charts.

Describe the bug

The Helm charts (tested with temporal-helm-charts v0.27.0) seem not to expose any way to configure secondaryVisibilityStore.
In particular, the server-configmap.yaml template only renders the primary visibility store, and there is no mechanism to define a secondary visibility section.

A previous PR (#779) attempted to add this feature but was closed without merging, and there is no clear alternative documented. It's unclear whether:

• dual visibility via Helm is intentionally unsupported,

• there is a different, recommended method to configure it, or

• the chart is simply missing template support.

Minimal Reproduction

Use a standard deployment of Temporal Server via the official Helm chart and attempt to define a second visibility store (both Elasticsearch).
There is no chart value or template path that renders configuration similar to:

persistence:
visibilityStore: es-visibility
secondaryVisibilityStore: es-secondary

Environment/Versions

OS and processor: Linux (x86_64)

Temporal Version: 1.29.0

Deployment method: Kubernetes using Helm charts (temporal-helm-charts v0.72.0)

Additional context

I originally planned to submit a PR to add this feature, but after noticing that PR #779 was closed, I’m unsure whether dual visibility is intentionally left unsupported in the charts or if a newer mechanism exists.
Any clarification on current support or recommended approach would be greatly appreciated.