-
Notifications
You must be signed in to change notification settings - Fork 238
NoCredentialProviders: no valid providers in chain #95
Comments
@maauso Are you ensuring that the server is running on separate nodes from the agent (e.g. via a |
@ewbankkit really?, so no, server and agent are running in the same nodes, because in EKS if I try to split them I found #94 problems. I opened a issue with aws and they are not sure if you can have more that one goup nodes, so nice. Thanks for you reply |
@ewantg you are right, the problem is related to have both parts in the same node, so I close this issue. Thanks for all |
Hi guys,
I am trying to run Kiam in EKS, we are using version 2.8, but we have the same error using version 2.7 in server side.
I created kiam-ubuntu-test role, with s3 admin rights, and Trust Relationship
When pod trys to run
aws s3 ls s3://something
we have the next error:Kiam Server side:
Kiam agent side
Take in consideration that :
1- EKS use amazon-vpc-cni
2.- Kiam server/agent are runing in worker nodes not in master
3.- We created the EKS cluster and Kiam services following the official documentation.
The text was updated successfully, but these errors were encountered: