-
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
CLI: HTTP client ignores proxy #10794
Comments
@Adam-D-Lewis Argo CLI will not support proxy-url. it might be coming from kubectl option. Do you like to implement it? |
Thanks for the response. Sorry, I can't commit to implement it right now. I've decided to pursue another option. |
This comment was marked as resolved.
This comment was marked as resolved.
I have implemented the feature, but I am unsure how to write tests for submitting a PR. Could you please give me some advice? |
I suppose this has been fixed by #12827 ...? |
Ah, no, this is about the CLI tool, so not re-opening. |
Pre-requisites
:latest
What happened/what you expected to happen?
Runnning
./argo-linux-amd64 submit -n dev hello-world.yaml --proxy-url http://localhost:8000 --argo-server <my-domain>:443 --argo-http1 --argo-base-href=/argo --token <my-token> --secure=true -v
outputs the curl command that is run which is
curl -X POST -H 'Authorization: ******' -d '{"namespace":"dev","workflow":{"kind":"Workflow","apiVersion":"argoproj.io/v1alpha1","metadata":{"generateName":"hello-world-","namespace":"dev","creationTimestamp":null,"labels":{"workflows.argoproj.io/archive-strategy":"false"},"annotations":{"workflows.argoproj.io/description":"This is a simple hello world example.\nYou can also run it in Python: https://couler-proj.github.io/couler/examples/#hello-world\n"}},"spec":{"templates":[{"name":"whalesay","inputs":{},"outputs":{},"metadata":{},"container":{"name":"","image":"docker/whalesay:latest","command":["cowsay"],"args":["hello world"],"resources":{}}}],"entrypoint":"whalesay","arguments":{}},"status":{"startedAt":null,"finishedAt":null}},"createOptions":{}}' 'https://<my-domain>:443/argo/api/v1/workflows/dev?'
As you can see the
--proxy-url
flag is ignored. I would have expected a-x http://localhost:8000
to be added to the curl command.Version
v3.4.5 (latest binary I could find)
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: