Skip to content

[Bug]: #892

@Akshaya-T

Description

@Akshaya-T

What happened?

Facing the below error and cannot connect to k8s

E0805 12:43:00.764344 14407 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0805 12:43:01.114905 14407 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0805 12:43:01.466005 14407 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0805 12:43:01.816481 14407 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
E0805 12:43:02.159087 14407 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: the server has asked for the client to provide credentials"
error: You must be logged in to the server (the server has asked for the client to provide credentials)

What you expected to happen?

Successful connection

Anything else we need to know?

In version 0.7.5 of aws-iam-authenticator I am facing the below error, whereas with 0.6.14 I am able to communicate with the cluster.

When I compared the retrieved token config I don't find any difference in the structure for both the versions, Just curious to understand what underlying change could have caused this issue.

Installation tooling

homebrew

AWS IAM Authenticator client version

{"Version":"0.7.5","Commit":"325c38ccbbd395e3bf612205809af77fe3f923ce"}

Client information

Kubernetes: I am using self hosted k8s managed through kops.
Client Version: v1.33.3
Server Version: v1.21.14

Kubernetes API Version

Client Version: v1.33.3 Kustomize Version: v5.6.0 Server Version: v1.21.14

kubeconfig user

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions