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

Unable to add an AWS EKS cluster : Question #12

Closed
satyamkapoor opened this issue Jul 9, 2019 · 11 comments
Closed

Unable to add an AWS EKS cluster : Question #12

satyamkapoor opened this issue Jul 9, 2019 · 11 comments
Assignees
Labels

Comments

@satyamkapoor
Copy link

I have an EKS cluster to which I connect from my machine using kubectl , AWS CLI and AWS IAM. I think it authenticates the user using the AWS IAM in my case.

When I try to add a resource, it detects the kubeconfig but upon clicking ADD SELECTED CLUSTERS, I receive a prompt - Failed to connect to arn:aws:eks:my-cluster-name platform cluster(s). Do you want to continue saving?

Can you please help how to resolve this?

Thanks!

@satyamkapoor satyamkapoor changed the title Unable to add an AWS EKS cluster Unable to add an AWS EKS cluster : Question Jul 9, 2019
@proAlexandr
Copy link
Contributor

proAlexandr commented Jul 9, 2019

Hi @satyamkapoor
Thank you that you use Kube Forwarder and for the bug report! I have investigated the problem some hours ago and I hope we will fix it in the next version within a week.

Details
  1. We have to update kubernetes-client/javascript version to 0.10.2 in order to apply the patch for aws-iam-authenticator not found when kube config contains exec env variables kubernetes-client/javascript#243
  2. kubernetes-client/javascript uses shelljs which has a problem with electron. We have to read this issue exec doesn't work in electron shelljs/shelljs#480 and figure out a workaround.

@proAlexandr proAlexandr added the bug label Jul 9, 2019
@proAlexandr proAlexandr self-assigned this Jul 9, 2019
@zen
Copy link

zen commented Jul 11, 2019

I have similar issue with GKE clusters. Looks like this problem would be very limiting for adoption, since AWS and GCP are 2 biggest platforms for managed k8s

@proAlexandr
Copy link
Contributor

The issue is fixed here bcfafd1. Will be released soon.

@lnikell
Copy link
Member

lnikell commented Jul 22, 2019

@satyamkapoor we've just released new version, could you please check it?

@lnikell
Copy link
Member

lnikell commented Jul 22, 2019

@zen also should work now with GKE as well

@satyamkapoor
Copy link
Author

satyamkapoor commented Jul 22, 2019

@satyamkapoor we've just released new version, could you please check it?

Hey, Thanks for the update. Just tried to initiate working with the application and got a bummer -

_Failed to connect to arn:aws:eks:eu-west-1:0000000000:cluster/my-cluster-name: aws: command not found. Please make sure you have installed AWS CLI. (https://docs.aws.amazon.com/cli/)

Do you want to continue saving?


Upon trying to add my 'docker for desktop' cluster, I get this message -
image

Am I doing something wrong?

@proAlexandr
Copy link
Contributor

proAlexandr commented Jul 22, 2019

Hi @satyamkapoor

_Failed to connect to arn:aws:eks:eu-west-1:0000000000:cluster/my-cluster-name: aws: command not found.

Do you install AWS CLI? For example brew install awscli.

Upon trying to add my 'docker for desktop' cluster, I get this message

This means that something with connection went wrong. Please, make sure that you enter the right credentials and your cluster is running.

@satyamkapoor
Copy link
Author

Hello,

I do have AWS cli installed and configured. Upon running brew install cli, it updated things but still the same error. :( Maybe just my system's issue

@emmenko
Copy link

emmenko commented Jul 23, 2019

I'm also having this problem (version 1.3.0).

Screenshot 2019-07-23 at 13 59 28

I do have aws-iam-authenticator installed:

image

My config looks like this:

users:
- name: <cluster_name>
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - token
      - -i
      - <token>
      command: aws-iam-authenticator
      env:
      - name: AWS_PROFILE
        value: <account_name>

@emmenko
Copy link

emmenko commented Jul 23, 2019

Nvm, I managed to solve this. I need to pass the full path to the command 🙈

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

@satyamkapoor
Copy link
Author

Thanks! Works great! I'm closing the issue.

proAlexandr added a commit that referenced this issue Jul 26, 2019
proAlexandr added a commit that referenced this issue Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants