Summary
The Argo Server Service currently has a hard‑coded targetPort: 2746 in the Helm chart template. I'd like to make this configurable via a new values parameter.
Use Case
When using TLS termination sidecars (e.g., nginx) in the Argo Server pod, the Service needs to route traffic to the sidecar's port (443) rather than the Argo Server container’s port (2746).
Current behaviour
The Service template hardcodes:
# charts/argo-workflows/templates/server/server‑service.yaml
ports:
- port: {{ .Values.server.servicePort }}
{{- with .Values.server.servicePortName }}
name: {{ . }}
{{- end }}
targetPort: 2746 # Hard‑codedDesired behaviour
Add a new server.serviceTargetPort value (defaulting to 2746 for backward compatibility):
server:
serviceTargetPort: 2746 # New configurable value
This would allow users deploying TLS sidecars or custom proxy containers to route traffic to the appropriate port.
Implementation
If maintainers are supportive of this change, I’m willing to implement it and submit a PR.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
Summary
The Argo Server Service currently has a hard‑coded
targetPort: 2746in the Helm chart template. I'd like to make this configurable via a new values parameter.Use Case
When using TLS termination sidecars (e.g., nginx) in the Argo Server pod, the Service needs to route traffic to the sidecar's port (443) rather than the Argo Server container’s port (2746).
Current behaviour
The Service template hardcodes:
Desired behaviour
Add a new
server.serviceTargetPortvalue (defaulting to 2746 for backward compatibility):This would allow users deploying TLS sidecars or custom proxy containers to route traffic to the appropriate port.
Implementation
If maintainers are supportive of this change, I’m willing to implement it and submit a PR.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.