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.

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

ENOENT Error with AWS EKS #60

Closed
FriedCircuits opened this issue Aug 23, 2019 · 5 comments · Fixed by #63
Closed

ENOENT Error with AWS EKS #60

FriedCircuits opened this issue Aug 23, 2019 · 5 comments · Fixed by #63
Labels

Comments

@FriedCircuits
Copy link

FriedCircuits commented Aug 23, 2019

I am trying to use kubebox with AWS EKS. I updated to 0.6.0 which supports the exec auth. I have been unsuccessful in connecting due to the following error:

spawn aws-iam-authenticator ENOENT

Pasting in a token doesn't seem to work either.

Any ideas? What am I missing?

@astefanutti
Copy link
Owner

It seems Kubebox is not able to execute aws-iam-authenticator. Could you try running:

$ which aws-iam-authenticator

Could you provide your kubeconfig details with the auth provider section as well.

@FriedCircuits
Copy link
Author

MacOS: /usr/local/bin/aws-iam-authenticator

contexts:
- context:
    cluster: eks-cluster
    user: aws
  name: aws
current-context: aws
kind: Config
preferences: {}
users:
- name: aws
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: aws-iam-authenticator
      args:
        - "token"
        - "-i"
        - "eks-cluster"
      env:
      - name: "AWS_PROFILE"
        value: "default"

@camilorivera
Copy link

Im presenting the same issue.

@johnpoth
Copy link
Collaborator

johnpoth commented Sep 4, 2019

There was an issue with setting environment variables see #63

You can workaround this by specifying the path to the executable in your kube config:

command: /usr/local/bin/aws-iam-authenticator

Thanks!

@FriedCircuits
Copy link
Author

Thanks everyone. Until there is a release I was able to get it to work with the workaround by specifying the full path for aws-iam-authenticator and aws binaries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants