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.

Sign up for GitHub

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

Jump to bottom

Bug: Incompatiblity of latest Helm version update in 0.12.57 and the AWS CLI version we ship in 0.12 #4571

Closed
stefreak opened this issue Jun 8, 2023 · 2 comments
Closed

Bug: Incompatiblity of latest Helm version update in 0.12.57 and the AWS CLI version we ship in 0.12 #4571

stefreak opened this issue Jun 8, 2023 · 2 comments
Assignees
@stefreak
Labels
bug triage/accepted

Comments

@stefreak
Copy link
Member

stefreak commented Jun 8, 2023

Bug

There seems to be an incompatibility with the latest Helm version and the AWS CLI version we ship in the workflow-runner image. (See also helm/helm#10975)

Current Behavior

When using the 0.12 garden container images starting with 0.12.57 together with AWS you get the error Error: Kubernetes cluster unreachable: exec plugin: invalid apiVersion "[client.authentication.k8s.io/v1alpha1](http://client.authentication.k8s.io/v1alpha1)"

Expected behavior

No error, it should work

Reproducible example

We can reproduce this internally

Workaround

Not really available for users; They can't easily upgrade the AWS CLI to v2 within the container, and they can't choose the helm version in Garden

Suggested solution(s)

Either we downgrade helm in 0.12 to 3.8 or we update the AWS CLI. I feel like preferring the latter even though it also has the potential to be breaking for some users. But the list of breaking changes in AWS CLI v1=>v2 is very small and we did not have trouble with it internally at all.

Additional context

Your environment

  • OS: macOS
  • How I'm running Kubernetes: AWS EKS

garden version 0.12.57
@stefreak stefreak self-assigned this Jun 8, 2023
@stefreak stefreak moved this to In Progress in Core Weekly Jun 8, 2023
@stefreak
Copy link
Member Author

stefreak commented Jun 8, 2023

Confirmed that this is an issue (successfully reproduced it internally)

stefreak added a commit that referenced this issue Jun 8, 2023
@stefreak
chore(deps): update AWS CLI, google cloud CLI and azure CLI to latest…
dc7ff2f 
… versions

This backports the new methods of installing the latest versions of AWS CLI, azure CLI and Google Cloud CLI from the main branch (Bonsai).

Fixes #4571 because there is an incompatibility between AWS CLI v1 and the latest helm versions.
@stefreak stefreak mentioned this issue Jun 8, 2023
Merged
stefreak added a commit that referenced this issue Jun 8, 2023
@stefreak
chore(deps): update AWS CLI, google cloud CLI and azure CLI to latest…
708e76f 
… versions (#4574)

This backports the new methods of installing the latest versions of AWS CLI, azure CLI and Google Cloud CLI from the main branch (Bonsai).

Fixes #4571 because there is an incompatibility between AWS CLI v1 and the latest helm versions.
@vvagaytsev vvagaytsev moved this from In Progress to Done in Core Weekly Jun 8, 2023
@vvagaytsev
Copy link
Collaborator

Fixed via #4574

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stefreak stefreak

Labels
bug triage/accepted
Projects
No open projects
Core Weekly
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stefreak @vvagaytsev