-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Feature/awscliv2 #31
base: master
Are you sure you want to change the base?
Feature/awscliv2 #31
Conversation
I'd like to keep both versions, I explained it in #10 We need keep compatible in this image.
can you adjust your codes to keep both versions? |
@ozbillwang added entrypoint script, results here: $ docker build -t k8s .
$ docker run -ti --rm -e awscli=v2 k8s aws --version
aws-cli/2.1.39 Python/3.8.8 Linux/5.10.76-linuxkit exe/x86_64.alpine.3 prompt/off
$ docker run -ti --rm k8s aws --version
aws-cli/1.22.96 Python/3.9.7 Linux/5.10.76-linuxkit botocore/1.24.41
$ docker run -ti --rm -e awscli=100500 k8s aws --version
aws-cli/1.22.96 Python/3.9.7 Linux/5.10.76-linuxkit botocore/1.24.41 I reread your message and reverted aws iam authenticator to Dockerfile for compatibility |
@ozbillwang, shall I make any other changes for this image? |
how can I use / test this? I am using AWS v2 and I can't get helm work on a k8s 1.22 cluster (AWS EKS). Wondering is it because AWS v1 is not supported anymore. Also the latest AWS v2 seems to be aws-cli/2.4.5. |
also maybe need to specify kubectl version (1.23.6) instead of latest |
So should we lock the aws v2 version in Dockerfile, or we can always install the latest version? I put the comments before. |
@ozbillwang have you checked this comment? |
oh, I missed that comment, let me check |
Is this PR abandoned, and is it missing something? |
Kinda abandoned I suppose 😃 If all packages are still available then it still should work |
Replaced aws-cli v1 with aws-cli v2.
aws-cli v2.1.39 is compatible with gcompat + groff
aws/aws-cli#4685