-
Notifications
You must be signed in to change notification settings - Fork 62
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
Action fails because incompatible python version for awscli #12
Comments
Same issue here!! Do you have a time limit to fix the issue ? |
Same here |
Same here! |
For anyone running into this issue and needing a fix asap, I had some issues when testing other kubectl github actions, but this works for AWS EKS:
|
Same here |
i've forked the repo and removed the aws dependency as we were not using it. if it's helpful for anybody NOT USING EKS you can find it here: https://github.com/marketplace/actions/kubernetes-kubectl-action-without-aws |
Hi @nacholemmo @ivilla @allancarvalho @VictorMessina @VictorMessina - Please try this and see if that works - https://github.com/marketplace/actions/kubernetes-action-with-python-2-x-fixes |
Same Here |
Same issue here but the fix from @davi020 has worked for us 🔥 |
HI, @davi020 , I have tried to user your version, it passed the previous error, but now I get which, after googling a bit seems to be connected with kubectl version issues, any idea? |
@nenadz-qsense I had the same issue at first. You'll need to update that line/value in your .kube/config file to this
Then base64 encode it again and update your secret. Worked perfectly for me after that 👍 Probably worth updating any versions of aws cli/kubectl locally/elsewhere too for consistency (if they are supported by your Kubernetes version/s) |
Hi @nenadz-qsense - Hope you fixed your issue with the solution @lomby provided. |
Currently I'm seeing this action fail with an error (see logs below).
I believe problem comes from this recent change in awscli package that removes support for python 2.7.
Wondering if/when issue will be corrected here. This is blocking my deployments so I need a fix asap.
The text was updated successfully, but these errors were encountered: