You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched the issue queue to verify this is not a duplicate feature request.
I've pasted the output of kargo version, if applicable.
I've pasted logs, if applicable.
Proposed Feature
Add a new parameter, rootPath, to allow serving the webapp and api from a different url path. For ArgoCD, we can use the following args to serve the web app at the /argo endpoint:
We currently use the same base url for all of our apps that are behind our reverse proxy. For example, argo cd would be hosted at https://base-url/argo, and kargo would be at https://base-url/kargo. However, without the ability to specify a base path for the backend server, the kargo web app would make request to https://base-url/assets, which wouldn't work with our reverse proxy. We need the request to go to https://base-url/kargo/assets.
Checklist
kargo version
, if applicable.Proposed Feature
Add a new parameter,
rootPath
, to allow serving the webapp and api from a different url path. For ArgoCD, we can use the following args to serve the web app at the /argo endpoint:Motivation
We currently use the same base url for all of our apps that are behind our reverse proxy. For example, argo cd would be hosted at
https://base-url/argo
, and kargo would be athttps://base-url/kargo
. However, without the ability to specify a base path for the backend server, the kargo web app would make request tohttps://base-url/assets
, which wouldn't work with our reverse proxy. We need the request to go tohttps://base-url/kargo/assets
.Suggested Implementation
Since we serve the frontend and backend from the same go server, we can use argo cd's approach here:
https://github.com/argoproj/argo-cd/blob/c09e6fa6ad2f48017e2d66e65a679226414e6653/server/server.go#L1122
(is there a reason we bundle everything (controller, backend, frontend etc) in the same docker container?)
The text was updated successfully, but these errors were encountered: