Skip to content
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

unable to get details for instance #366

Open
sandeepnanda2 opened this issue Aug 6, 2020 · 2 comments
Open

unable to get details for instance #366

sandeepnanda2 opened this issue Aug 6, 2020 · 2 comments
Labels

Comments

@sandeepnanda2
Copy link

unable to get details for instance "i-xxxxxxxxxx": NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors

I have executed kubectl create -f deploy/ingress-controller.yaml As a result my pod(kube-ingress-aws-controller) went in CrashLoopBackOff with above error string.

@mikkeloscar
Copy link
Collaborator

The example assumes an IAM role is configured using kube2iam:

iam.amazonaws.com/role: arn:aws:iam::12345678901:role/YOUR_PRECONFIGURED_ROLE

If you're not using that you need another way to configure the AWS IAM role.

@sandeepnanda2
Copy link
Author

sandeepnanda2 commented Aug 12, 2020

Hi @mikkeloscar ,
Yes IAM is configured using kube2iam,
and replaced at Line 22 iam.amazonaws.com/role: arn:aws:iam::12345678901:role/YOUR_PRECONFIGURED_ROLE.
Could you please advice what needs to be done.
I'm completely new to devops.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants