Is your feature request related to a problem?

There have been reports that running Argo Workflows behind a reverse proxy on a subpath (e.g., /workflows) requires configuring path rewrites at the proxy level. This becomes problematic in environments such as AWS Application Load Balancer, which does not support path rewrites. Unlike Argo CD—which supports subpath deployments using --rootpath and --basehref flags—Argo Workflows lacks equivalent options, making such setups more difficult and inconsistent across the Argo ecosystem.

Related helm chart

argo-workflows

Describe the solution you'd like

Expose a new server.rootPath field in the Argo Workflows Helm chart’s values.yaml to support subpath deployments.

• Pass this value as the ARGO_ROOT_PATH environment variable to the server container.
• Update the readiness probe path in the deployment manifest to respect the configured root path.
• Set a default value of / to ensure backward compatibility.
  This enhancement will allow users to configure a custom root path through Helm values without needing to manually patch manifests, improving flexibility in reverse proxy environments.

Describe alternatives you've considered

No response

Additional context

No response