Invalid clusterMetadata rpcAddress?

[emmercm]

What are you really trying to do?

Debug an inconsistent connectivity issue where I have two different Temporal clusters both with a clusterMetadata.clusterInformation.rpcAddress = "127.0.0.1:7933".

Describe the bug

helm-charts/templates/server-configmap.yaml

Line 156 in e5f0942

rpcAddress: "127.0.0.1:7933"

I don't believe any service listens on port 7933. I see evidence that this is a carry-over from Cadence days: temporalio/temporal#650.

Is that port in the Helm charts correct? Should I be using the frontend DNS name coming from {{ include "temporal.componentname" (list $ "frontend") }} instead of localhost?

Minimal Reproduction

I've been struggling to reproduce connectivity issues on my end, but sometimes when servers restart they lose connection with each other.

Environment/Versions

Temporal v1.18.1, using official Docker images and mostly official Helm charts.

Additional context

[emmercm]

This is potentially a duplicate of #149.