Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2020-12-13 08:41:16
Size: 104
Editor: PieterSmit
Comment:
Revision 3 as of 2022-02-24 22:17:59
Size: 1068
Editor: PieterSmit
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe k8s/AwsEks here. = k8s kubernetes on AWS AWSEKS =
 * Terraform example1 [[https://www.padok.fr/en/blog/aws-eks-cluster-terraform]]
 * Terraform example2 [[https://github.com/hashicorp/terraform-provider-aws/tree/master/examples/eks-getting-started]]
   * 202012 - worked, only changed region and setup aws credentials.
     * Creates new VPC and 2 subnets for k8s deployment
       * Took 11min for management node to deploy
 * aws eks --region <region-code> update-kubeconfig --name <cluster_name>
Line 3: Line 9:
 * aws eks --region <region-code> update-kubeconfig --name <cluster_name>
== Recover admin login ==
 1. Can you see the cluster (check correct AWS_Profile) {{{
aws eks list-clusters
}}}
 1. Make sure current role does not work by retrieveing kubectl config {{{
aws eks update-kubeconfig --region ap-southeast-2 --name "eks-cluster-name"
kubectl get svc
error: You must be logged in to the server (Unauthorized)
}}}
 1. Have to assume the original admin account/role
    * How to find the admin account / role ?
      1. install eksctl https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html
      2. retrieve accounts {{{


}}}

k8s kubernetes on AWS AWSEKS

Recover admin login

  1. Can you see the cluster (check correct AWS_Profile)

    aws eks list-clusters
  2. Make sure current role does not work by retrieveing kubectl config

    aws eks update-kubeconfig --region ap-southeast-2 --name "eks-cluster-name"
    kubectl get svc
    error: You must be logged in to the server (Unauthorized)
  3. Have to assume the original admin account/role

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