Argo S3 artifacts don't work when minio client needs to assume role #11723
Labels
area/artifacts
S3/GCP/OSS/Git/HDFS etc
go
Pull requests that update Go dependencies
type/bug
type/dependencies
PRs and issues specific to updating dependencies
type/regression
Regression from previous behavior (a specific type of bug)
Pre-requisites
:latest
What happened/what you expected to happen?
Expected:
Happened:
http://169.254.169.254/latest/api/token": context deadline exceeded
This happens if the EC2 instances is not enabled for IMDSv2 and was introduced as part of this PR on minio-go and was merged in Argo v3.4.0. It has since been fixed and released as a BugFix version v7.0.63. We will need to just update the the minio dependency to fix it.
Version
v3.4.9 and latest
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: