Please support AWS Authenticator for EKS

[spiffytech]

Amazon EKS requires the user generates a token through the AWS Authenticator, using the exec option on the user property in the kubeconfig file. kubernetes-client does not appear to support this option, so we cannot use it to talk to our EKS clusters.

https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html

[silasbw]

We need to support this. We're also planning on adopting EKS.

[cfellin1]

On it.

[faizhasim]

This is my workaround for my development setup. The idea is to create (or reuse) a ServiceAccount and use the ServiceAccount token to authenticate. So, instead of doing this:

  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - token
      - -i
      - myclustername
      command: heptio-authenticator-aws

I would, configure directly with the ServiceAccount token:

user:
    token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

In my development cluster, I have access to Tiller serviceaccount, so I just get the serviceaccount token secret and configure a new KUBECONFIG. I modified my code a bit to help development:

const kubeConfig = () => {
  if (isInCluster()) {
    return config.getInCluster()
  } else if (process.env.KUBECONFIG) {
    return config.fromKubeconfig(config.loadKubeconfig(process.env.KUBECONFIG))
  } else {
    return config.fromKubeconfig()
  }
}