[Bug]: Fix to #606 not available in released version, eksctl quickstart instructions doesn't work with new style SSO config

[nresare]

What happened?

I just wanted to bring attention to the fact that the currently released versions of aws-iam-authenticator fails to provide authentication to users that have set up authentication using the recommended SSO authentication method.

This problem was described in #606 back in June and addressed in master with commit 56b684c in late August. However this update has not been included in any released version of this project, which is unfortunate since the AWS on-boarding documentation encourages users to use the IAM Identity Center.

In other words, a newly signed up AWS user that sets up IAM Identity Center to authenticate, installs the latest released versions of awscli, eksctl (using for example homebrew) and uses something like eksctl create cluster --name my_cluster --region eu-north-1 --fargate will end up with a Kubernetes configuration where a trivial kubectl get ns fails with the following somewhat cryptic error message:

could not get token: could not create session: profile "default" is configured to use SSO but is missing required configuration: sso_region, sso_start_url

I have verified that cherry-picking 56b684c onto the v0.6.12 release resolves this problem

What you expected to happen?

I would expect a new user that follows the recommended steps in the AWS on-boarding documentation with the latest released software to succeed connecting to the EKS cluster that gets created when following the on boarding steps.

Anything else we need to know?

No response

Installation tooling

homebrew

AWS IAM Authenticator client version

0.6.12

Client information

- OS/arch: macos, arm64
- kubernetes client & version: default from eksctl

Kubernetes API Version

Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.9", GitCommit:"a1a87a0a2bcd605820920c6b0e618a8ab7d117d4", GitTreeState:"clean", BuildDate:"2023-04-12T12:16:51Z", GoVersion:"go1.19.8", Compiler:"gc", Platform:"darwin/arm64"}

kubeconfig user

No response

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.