1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
The error may be related to the path of the kubeconfig. Can u please check the path of the kubeconfig. and if this seems to be correct then This could be because the cluster was created with credentials for one IAM principal and kubectl is using credentials for a different IAM principal. To get more information about this refer to this: Unauthorized or access denied (kubectl).
답변함 일 년 전
관련 콘텐츠
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 3년 전
Hi, it's not the kubeconfig path - I've used kubectl with other providers for a while no w/ no issues.
The troubleshooting page that you linked recommends creating a kubeconfig using a role. I attempted this (my last screenshot) and it still didn't authenticate. I've fixed it in the short term by adding my low priv user to the cluster directly with eksctl and a userarn mapUsers entry, but my question is can I authenticate directly with the role as the docs imply.