argoproj / argoproj/argo-workflows

Implement rootpath similar to argo-cd

Open
#7,767 3 comments 11 reactions 0 assignees View on GitHub
area/server area/ui solution/suggested
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

# Summary

Currently, running argo-workflows on a subpath requires rewrites on the reverse proxy. In argo-cd you can avoid that by setting extra arguments to the entrypoint command.
```
- --rootpath
- /argocd
- --basehref
- /argocd
```
Would it be possible to replicate this behavior on argo-workflows as well?

# Use Cases

AWS Application Load Balancers do not support rewrites. Our setup doesn't use any additional controller like nginx.

---

**Message from the maintainers**:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the argo-workflows entrypoint command and the handling of request paths, links, and assets, then compare the requested --rootpath and --basehref behavior with argo-cd. Identify the relevant tests before making changes. Done means the service works from a configured subpath without reverse-proxy rewrites, including navigation and static assets.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.