aws / aws/eks-anywhere

Package Installation Fails on workload cluster with IAM Auth kubeconfig

Open
#3,305 3 comments 0 reactions 0 assignees View on GitHub
area/packages/controller team/packages
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What happened**:
Installing package controller when using AWS IAM Auth kubeconfig returns the following error:
```
eksctl anywhere install packagecontroller -f $CLUSTER_NAME.yaml
Error: Unable to connect to the server: getting credentials: exec: executable aws-iam-authenticator not found

It looks like you are trying to use a client-go credential plugin that is not installed.

To learn more about this feature, consult the documentation available at:
https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins
```

**What you expected to happen**:
Package installation to work

**How to reproduce it (as minimally and precisely as possible)**:
Create a IAM Auth enabled workload cluster and set the `KUBECONFIG` env var to the IAM Auth kubeconfig

**Anything else we need to know?**:

**Environment**:
- EKS Anywhere Release: v0.11.1
- EKS Distro Release: v1.23

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the `eksctl anywhere install packagecontroller -f $CLUSTER_NAME.yaml` command with `KUBECONFIG` set to an IAM Auth workload-cluster kubeconfig, then trace the package-controller installation entry point and its client credential handling. Done means package installation succeeds without requiring an unavailable `aws-iam-authenticator` executable.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go
Domain
authentication, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.