Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting base-href to "/argo/" and then accessing via portforward does not work. #11643

Closed
2 of 3 tasks
ramanNarasimhan77 opened this issue Aug 21, 2023 · 3 comments
Closed
2 of 3 tasks
Labels
area/server solution/duplicate This issue or PR is a duplicate of an existing one type/support User support issue - likely not a bug

Comments

@ramanNarasimhan77
Copy link

Pre-requisites

  • I have double-checked my configuration
  • I can confirm the issues exists when I tested with :latest
  • I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?

I installed https://github.com/argoproj/argo-workflows/blob/master/manifests/quick-start-minimal.yaml

Made the following changes.

  1. Added extra server argument --insecure=true for testing without tls
  2. Added env BASE_HREF as /argo/
  3. Changed HTTPS to HTTP in container probe

image

I port-forwarded Argo-server:2746 to localhost:2747 and got blank page

image

I expected to be able to see the Argo home page at "/argo/"

Version

latest

Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

NA

Logs from the workflow controller

kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

NA

Logs from in your workflow's wait container

kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

NA
@agilgur5
Copy link
Member

agilgur5 commented Aug 21, 2023

Looks like a duplicate of #10194 which I literally just answered 😅

@agilgur5
Copy link
Member

agilgur5 commented Aug 21, 2023

From your screenshot, the HTML has <base href="/argo/">, so that is working correctly.

Per my most recent comment in #10194, you might be looking for rootpath support, i.e. #7767

@ramanNarasimhan77
Copy link
Author

Thank you for the clarification @agilgur5

@agilgur5 agilgur5 added solution/duplicate This issue or PR is a duplicate of an existing one solution/suggested A solution to the bug has been suggested. Someone needs to implement it. area/server and removed type/bug solution/suggested A solution to the bug has been suggested. Someone needs to implement it. labels Sep 2, 2023
@agilgur5 agilgur5 added the type/support User support issue - likely not a bug label Sep 11, 2023
@argoproj argoproj locked as resolved and limited conversation to collaborators Jun 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/server solution/duplicate This issue or PR is a duplicate of an existing one type/support User support issue - likely not a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants