-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
ui: getPodName is using v1 by default #11015
Comments
@JPZ13 can you take a look? |
terrytangyuan
pushed a commit
that referenced
this issue
May 12, 2023
44 tasks
terrytangyuan
pushed a commit
that referenced
this issue
May 25, 2023
JPZ13
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Jul 4, 2023
) (argoproj#11016) Signed-off-by: or-shachar <or.shachar@wiz.io>
dpadhiar
pushed a commit
to dpadhiar/argo-workflows
that referenced
this issue
May 9, 2024
) (argoproj#11016) Signed-off-by: or-shachar <or.shachar@wiz.io> Signed-off-by: Dillen Padhiar <dillen_padhiar@intuit.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
I noticed that for some workflows the podName is wrongfully set as the nodeID (which is the v1 format).
This resulted in bad log streaming for running templates. (I thought it was related to #10124 but I think it's a pure UI issue).
Looking at the ts code I saw this condition:
argo-workflows/ui/src/app/shared/pod-name.ts
Line 14 in 0c24ca1
The
version
here is taken straight from the direct annotation of the workflow:argo-workflows/ui/src/app/archived-workflows/components/archived-workflow-details/archived-workflow-details.tsx
Line 56 in 133b4a3
I think that after cc9d14c we should change the condition so that v2 would be used by default also for UI.
Version
v3.4.5
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.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: