-
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
env http_proxy
in wait/init container does not work for oss client
#12313
Labels
area/artifacts
S3/GCP/OSS/Git/HDFS etc
P2
Important. All bugs with >=3 thumbs up that aren’t P0 or P1, plus: Any other bugs deemed important
type/bug
Milestone
Comments
Would you like to submit a PR? |
jingkkkkai
added a commit
to jingkkkkai/argo-workflows
that referenced
this issue
Dec 18, 2023
Signed-off-by: Jingkai Hung <[email protected]>
I opened a PR, can you help me review it? |
agilgur5
added
P2
Important. All bugs with >=3 thumbs up that aren’t P0 or P1, plus: Any other bugs deemed important
and removed
P3
Low priority
labels
Jul 2, 2024
jingkkkkai
added a commit
to jingkkkkai/argo-workflows
that referenced
this issue
Aug 20, 2024
Signed-off-by: Jingkai Hung <[email protected]>
jingkkkkai
added a commit
to jingkkkkai/argo-workflows
that referenced
this issue
Sep 2, 2024
Signed-off-by: Jingkai Hung <[email protected]>
jingkkkkai
added a commit
to jingkkkkai/argo-workflows
that referenced
this issue
Sep 2, 2024
Signed-off-by: Jingkai Hung <[email protected]>
terrytangyuan
pushed a commit
that referenced
this issue
Sep 10, 2024
…2383) Signed-off-by: Jingkai Hung <[email protected]>
agilgur5
changed the title
env http_proxy in wait/init container does not work for oss client
env Sep 10, 2024
http_proxy
in wait/init container does not work for oss client
Joibel
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Sep 19, 2024
…2313 (argoproj#12383) Signed-off-by: Jingkai Hung <[email protected]>
Joibel
pushed a commit
that referenced
this issue
Sep 20, 2024
…2383) Signed-off-by: Jingkai Hung <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/artifacts
S3/GCP/OSS/Git/HDFS etc
P2
Important. All bugs with >=3 thumbs up that aren’t P0 or P1, plus: Any other bugs deemed important
type/bug
Pre-requisites
:latest
What happened/what did you expect to happen?
in my
workflow-controller-configmap
had configurehttp_proxy
https_proxy
and it can access
gcs
s3
artifact repository correctly, except foross
artifact repositoryI created a test pod with setting the same proxy, I found that the oss-cli cannot not access the oss either
but I can access the oss bucket after applying the args
--proxy-host
Ref: aliyun http proxy
The oss client in the argo code seems in the same case. The proxy can only be set through
oss.ClientOption
However, we cannot configure the proxy for oss client through pod env or
argoexec
args currentlyVersion
v3.4.8 & v3.4.14
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.
N/A
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: