Hi Temporal team,
[note: I opened this issue with the help of AI]
Could the chart expose Kubernetes Service.spec.trafficDistribution as a configurable value for the server services (at least server.frontend.service, and ideally the other server service blocks too)?
I verified this is still not supported in:
temporal-1.1.1 (latest release as of 2026-04-22)
main
Today, charts/temporal/templates/server-service.yaml renders the service spec with fields like type, ports, and selector, but it does not template trafficDistribution.
Likewise, charts/temporal/values.yaml exposes fields under server.<service>.service such as:
annotations
type
port
appProtocol
membershipPort
membershipAppProtocol
httpPort
httpAppProtocol
but not trafficDistribution.
That means values like this are currently a no-op:
server:
frontend:
service:
trafficDistribution: PreferClose
Our current workaround is to let Helm manage the Service and then apply a separate server-side-apply patch just for spec.trafficDistribution, which works but is not as clean as having first-class chart support.
It would be great if the chart supported something like:
server:
frontend:
service:
trafficDistribution: PreferClose
and rendered it only when set.
This would help users adopt the newer native Service traffic-distribution behavior without needing a chart fork or an out-of-band manifest patch.
Thanks!
Hi Temporal team,
[note: I opened this issue with the help of AI]
Could the chart expose Kubernetes
Service.spec.trafficDistributionas a configurable value for the server services (at leastserver.frontend.service, and ideally the other server service blocks too)?I verified this is still not supported in:
temporal-1.1.1(latest release as of 2026-04-22)mainToday,
charts/temporal/templates/server-service.yamlrenders the servicespecwith fields liketype,ports, andselector, but it does not templatetrafficDistribution.Likewise,
charts/temporal/values.yamlexposes fields underserver.<service>.servicesuch as:annotationstypeportappProtocolmembershipPortmembershipAppProtocolhttpPorthttpAppProtocolbut not
trafficDistribution.That means values like this are currently a no-op:
Our current workaround is to let Helm manage the Service and then apply a separate server-side-apply patch just for
spec.trafficDistribution, which works but is not as clean as having first-class chart support.It would be great if the chart supported something like:
and rendered it only when set.
This would help users adopt the newer native Service traffic-distribution behavior without needing a chart fork or an out-of-band manifest patch.
Thanks!