install-aws-iam-authenticator command fails on newest aws-iam-authenticator release about aws-eks-orb HOT 10 CLOSED

Maybe orb could freeze this binary in lastest version in every release? In CIs, it seems preferable to choose stability over other trade offs.

from aws-eks-orb.

Just found out that aws-eks: circleci/[email protected] will work now, as they removed the indirect reference in the bash script. So now if you use that version you just need to set the tag version without jumping through hoops!

      - aws-eks/update-container-image:
          name: name
          authenticator-release-tag: "0.6.11"

from aws-eks-orb.

Work-around for the meantime, i've added this. Which installs aws-iam-authenticator and kubectl manually:

      - run:
          command: |
            curl -o aws-iam-authenticator https://s3.us-west-2.amazonaws.com/amazon-eks/1.21.2/2021-07-05/bin/linux/amd64/aws-iam-authenticator
            chmod +x ./aws-iam-authenticator
            mkdir -p $HOME/bin && cp ./aws-iam-authenticator $HOME/bin/aws-iam-authenticator && export PATH=$PATH:$HOME/bin
            echo 'export PATH=$PATH:$HOME/bin' >> ~/.bashrc
            aws-iam-authenticator help
            curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
            sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl
            kubectl version --client

Add this before aws-eks/update-kubeconfig-with-authenticator step

from aws-eks-orb.

I have another work around, although I still think that the original bash script should be fixed...

Add an environment varible to your Circle CI project called AWS_AUTHENTICATOR_VARIABLE (or whatever you want) that resolves to the target version. In my case I needed to use 0.6.11 because 0.6.12 is missing binaries.

In your Workflow jobs set authenticator-release-tag: "AWS_AUTHENTICATOR_VARIABLE" like so:

      - aws-eks/update-container-image:
          name: name
          authenticator-release-tag: "AWS_AUTHENTICATOR_VARIABLE"

Then in your jobs where you are defining your Docker image do something like this:

  run_command:
    docker:
      - image: "cimg/python:3.11.4"
        environment:
          AWS_AUTHENTICATOR_VARIABLE: $AWS_AUTHENTICATOR_VARIABLE

This will ensure that you can set the variable on the project, and then you can properly get around the indirect reference in the bash script.

from aws-eks-orb.

Supposedly the following should fix it (by locking to the previous release), but it doesn't appear to work for me, and still tries to download the latest:

- aws-eks/update-kubeconfig-with-authenticator:
    authenticator-release-tag: v0.5.6

from aws-eks-orb.

Supposedly the following should fix it (by locking to the previous release), but it doesn't appear to work for me, and still tries to download the latest:

- aws-eks/update-kubeconfig-with-authenticator:
    authenticator-release-tag: v0.5.6

try this maybe: authenticator-release-tag: "v0.5.6" it worked for us like that

from aws-eks-orb.

I added check for latest version of authenticator with binary release
#63

from aws-eks-orb.

Supposedly the following should fix it (by locking to the previous release), but it doesn't appear to work for me, and still tries to download the latest:

- aws-eks/update-kubeconfig-with-authenticator:
    authenticator-release-tag: v0.5.6

try this maybe: authenticator-release-tag: "v0.5.6" it worked for us like that

Unfortunately this does not work for us.

from aws-eks-orb.

I'm getting /bin/bash: line 13: v0.5.6: invalid variable name when using authenticator-release-tag: v0.5.6, both with and without the quotes. (using orb version 2.1.1)

from aws-eks-orb.

authenticator-release-tag: v0.5.6 works if you you downgrade your orb version to 1.2.0, aws-eks: circleci/[email protected]

from aws-eks-orb.