Differences between revisions 4 and 5
Revision 4 as of 2022-03-13 06:30:01
Size: 1282
Editor: PieterSmit
Comment:
Revision 5 as of 2022-03-13 06:51:48
Size: 1569
Editor: PieterSmit
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 1. You need to know the IAM role/user that created the cluster. (Maybe look in your Terraform)
Line 13: Line 14:
# or if installed
eksctl get cluster
# or if installed $ eksctl get cluster
Line 16: Line 16:
 1. Make sure current role does not work by retrieveing kubectl config {{{
aws eks update-kubeconfig --region ap-southeast-2 --name "eks-cluster-name"
 1. Make sure current role does not work by retrieving kubectl config {{{
aws eks update-kubeconfig --region ap-southeast-2 --name "eks-cluster-name" --role-arn "arn:aws:iam::123456789:role/myk8srole"
Line 19: Line 19:
error: You must be logged in to the server (Unauthorized)
Line 21: Line 20:
 1. '''''error: You must be logged in to the server (Unauthorized)'''''
   * This error indicates that the role you used, is not in system:management, thus not the one that created the cluster.

k8s kubernetes on AWS AWSEKS

Recover admin login

  1. You need to know the IAM role/user that created the cluster. (Maybe look in your Terraform)
  2. Can you see the cluster (check correct export AWS_PROFILE=)

    aws eks list-clusters
    # or if installed $ eksctl get cluster
  3. Make sure current role does not work by retrieving kubectl config

    aws eks update-kubeconfig --region ap-southeast-2 --name "eks-cluster-name" --role-arn "arn:aws:iam::123456789:role/myk8srole"
    kubectl get svc
  4. error: You must be logged in to the server (Unauthorized)

    • This error indicates that the role you used, is not in system:management, thus not the one that created the cluster.
  5. AWS doc for Unauthorized or access denied (kubectl)

  6. Have to assume the original admin account/role

k8s/AwsEks (last edited 2022-03-13 06:51:48 by PieterSmit)