-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Not working for showing groups information #18
Comments
Hi @posquit0 thanks for reporting the issue. is it possible for you to please submit a PR for this? I don't have access to EKS cluster setup. Thanks |
I just tried with onelogin OIDC provider + EKS, and it seems to have worked. and showing me all groups that I am part of. could you please try once more. |
Hi, thank you for following this issue. I'm so glad to hear that. What is your configuration for |
i am using a custom login plugin instead of oidc-login, but i don't think that matters. We make use of k8s api calls to fetch whoami info. could you please add some logging on your laptop and help submit a PR for this? |
I found a solution for a related issue, in order for kubectl-whoami to show the ARN information for a user,
Without this rule within a ClusterRole assigned to that user, Sorry if this isn't relevant, but I did see that both printing Groups and ARNs are within the same |
Problem
It works when I try
kubectl whoami --all
command to AWS EKS cluster viaaws-iam-authenticator
default authentication method.It doesn't work when I try
kubectl whoami --all
command to AWS EKS cluster via different OIDC Identity Provider authentication. In my case, I tried with Okta OIDC identity provider. The output is same withkubectl whoami
command.The text was updated successfully, but these errors were encountered: