[CI] Included a step to install aws-iam-authenticator #9128
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
Fix MLRun enterprise system-tests pod log collection failures caused by EKS exec-auth issues:
Ensure the system-tests CI container has the required aws-iam-authenticator binary (kubeconfig exec plugin).
Make pod-log collection more robust on long runs by refreshing kubeconfig and retrying once on 401 Unauthorized (expired EKS token).
🛠️ Changes Made
CI: Install aws-iam-authenticator into the run-system-tests-enterprise-ci container and add curl dependency (required by kubeconfig exec auth).
✅ Checklist
🧪 Testing
Ran enterprise system tests in CI and validated:
kubeconfig exec auth no longer fails with No such file or directory: aws-iam-authenticator
on test failures after long runtime, pod log collection no longer fails with 401 Unauthorized and logs are printed
🔗 References
🚨 Breaking Changes?