Closed esn89 closed 3 months ago
You filed this as a bug, but this is not an Argo bug. The Server works and has E2E tests on CI, is used during dev, and many people have it working, including in the Ingress examples you linked.
You also had it working yourself on Slack. So this is an Ingress/Istio GW/VS configuration issue and not an Argo bug.
As the "Create a new issue" chooser says, issues are for bugs, while Slack and Discussions are for support. You already have a Slack thread and did receive some debugging help from the community already.
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
Downloaded, installed Argo Workflows 3.5.10, with
secure=false
andBASE_HREF=/
behind Istio, gives errors of:upstream connect error or disconnect/reset before headers. retried and the latest reset reason: connection failure
Or, it just loads a blank page
Version(s)
3.5.10
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
No workflows yet being that I wasn't even able to get to that part
What I can tell you is that, I have set:
--secure false
withBASE_HREF=/
.On Istio Gateway:
VirtualService:
Kubernetes Service:
Logs from the workflow controller
Logs from in your workflow's wait container
I also took a look and did some searching and saw something similar here: https://github.com/argoproj/argo-workflows/issues/3080#issuecomment-1278072332 from @arnoldrw and @agilgur5 , I tried that but to no avail.