buildkite / feedback

Got feedback? Please let us know!
https://buildkite.com
25 stars 24 forks source link

Issue: kubectl not working iwth aws eks|Botocore version for aws cli #518

Open ld-singh opened 4 years ago

ld-singh commented 4 years ago

Hi, On my buildkite AWS agents the below command stopped working since Friday (25th October 2019)

aws eks get-token --cluster-name --region

I am getting 'credentialsScope' message as result of any kubectl command and no result. This command is utilised by kubectl via config file to connect to my cluster which is generated with aws eks update-config command (https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html)

This was working fine before. The version of aws (default one that comes with AMI) is: aws-cli/1.16.169 Python/2.7.16 Linux/4.14.121-109.96.amzn2.x86_64 botocore/1.13.2

In order to replicate I tried installing same aws-cli version on another amazon linux. But i get installed as follows (please note botocore version) and works absolutely fine with kubectl aws-cli/1.16.169 Python/2.7.16 Linux/4.14.138-114.102.amzn2.x86_64 botocore/1.12.159

When i tried installing same botocore version as buildkite agent, i could not do it as I got the below error: ERROR: awscli 1.16.169 has requirement botocore==1.12.159, but you'll have botocore 1.13.2 which is incompatible.

Could you please let me know if any changes has been done in buildkite agent AMI recently because of which kubectl has stopped working with aws eks command?