-
Hello We are currently doing our first steps with argo workflow. Our cluster is behind a proxy. The url of the proxy is dynamically generated and is changing from time to time. Every time the url is stored in a secret on the cluster, so it can be consumed by deployments or other configurations. We can set the proxy url (http_proxy/https_proxy) from this secret without issues for a workflow template, by using the approach (https://argoproj.github.io/argo-workflows/walk-through/secrets/) described in the walk-through. However, when using S3 as repository for Artifacts we still get a timeout from the wait container sidecar. We noticed, that the wait container sidecar does not have the environment variables, defined for the workflow template. They are only set for the main container. Is there any way to set the environment variables for the wait sidecar container, so that we don't get timeouts when using S3 as artifact repository? We could not find a clear answer in the documentation. Thanks for the help, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The Within the You might also be able to do this at a template-level using |
Beta Was this translation helpful? Give feedback.
The
wait
container is an executor container (along with theinit
container). Within a template, there are currently only a few explicit options to configure theexecutor
.Within the
workflow-controller-configmap
, more options are available, includingenv
.You might also be able to do this at a template-level using
podSpecPatch
to override theenv
.