태스크 2: Amazon EKS 클러스터 생성

이 글은 스킬빌더 내용 바탕으로 제가 출력한 값을 넣은 글입니다. 오해 없길 바랍니다.

 

이 태스크에서는 eksctl 명령을 사용하여 실습 계정에 Amazon EKS 클러스터 및 전용 Virtual Private Cloud(VPC)를 생성합니다. eksctl 명령에 관한 자세한 내용을 알아보려면 다음을 참조하십시오.

• Amazon EKS 시작하기 – eksctl
• eksctl 소개

1. 명령: Amazon EKS 클러스터를 생성하려면 AWS Cloud9 터미널에서 다음 명령을 실행합니다.

eksctl create cluster \\
--name eks-lab-cluster \\
--nodegroup-name worknodes-1 \\
--node-type t3.medium \\
--nodes 2 \\
--nodes-min 1 \\
--nodes-max 4 \\
--managed \\
--version 1.26 \\
--region ${AWS_DEFAULT_REGION}

---

퍼미션 문제가 생길 때 에러 조치 방법

 

Credentials off 상태

 

 

 

Experimental Features(Auto-Save Files→ On Focus change)'

 

 

AWS nof found

eksetup.sh 19번째를 지우고 실행

 

 

예상 출력

******************************
**** This is OUTPUT ONLY. ****
******************************

2023-07-25 19:24:27 [ℹ]  eksctl version 0.150.0-dev
2023-07-25 19:24:27 [ℹ]  using region us-west-2
2023-07-25 19:24:27 [ℹ]  setting availability zones to [us-west-2d us-west-2a us-west-2b]
2023-07-25 19:24:27 [ℹ]  subnets for us-west-2d - public:192.168.0.0/19 private:192.168.96.0/19
2023-07-25 19:24:27 [ℹ]  subnets for us-west-2a - public:192.168.32.0/19 private:192.168.128.0/19
2023-07-25 19:24:27 [ℹ]  subnets for us-west-2b - public:192.168.64.0/19 private:192.168.160.0/19
2023-07-25 19:24:27 [ℹ]  nodegroup "worknodes-1" will use "" [AmazonLinux2/1.25]
2023-07-25 19:24:27 [ℹ]  using Kubernetes version 1.25
2023-07-25 19:24:27 [ℹ]  creating EKS cluster "eks-lab-cluster" in "us-west-2" region with managed nodes
2023-07-25 19:24:27 [ℹ]  will create 2 separate CloudFormation stacks for cluster itself and the initial managed nodegroup
2023-07-25 19:24:27 [ℹ]  if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --cluster=eks-lab-cluster'
2023-07-25 19:24:27 [ℹ]  Kubernetes API endpoint access will use default of {publicAccess=true, privateAccess=false} for cluster "eks-lab-cluster" in "us-west-2"
2023-07-25 19:24:27 [ℹ]  CloudWatch logging will not be enabled for cluster "eks-lab-cluster" in "us-west-2"
2023-07-25 19:24:27 [ℹ]  you can enable it with 'eksctl utils update-cluster-logging --enable-types={SPECIFY-YOUR-LOG-TYPES-HERE (e.g. all)} --region=us-west-2 --cluster=eks-lab-cluster'
2023-07-25 19:24:27 [ℹ]  
2 sequential tasks: { create cluster control plane "eks-lab-cluster", 
    2 sequential sub-tasks: { 
        wait for control plane to become ready,
        create managed nodegroup "worknodes-1",
    } 
}
2023-07-25 19:24:27 [ℹ]  building cluster stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:24:27 [ℹ]  deploying stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:24:57 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:25:27 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:26:27 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:27:27 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:28:27 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:29:27 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:30:28 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:31:28 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:32:28 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:33:28 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:34:28 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-cluster"
2023-07-25 19:36:29 [ℹ]  building managed nodegroup stack "eksctl-eks-lab-cluster-nodegroup-worknodes-1"
2023-07-25 19:36:29 [ℹ]  deploying stack "eksctl-eks-lab-cluster-nodegroup-worknodes-1"
2023-07-25 19:36:29 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-nodegroup-worknodes-1"
2023-07-25 19:36:59 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-nodegroup-worknodes-1"
2023-07-25 19:37:52 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-nodegroup-worknodes-1"
2023-07-25 19:39:11 [ℹ]  waiting for CloudFormation stack "eksctl-eks-lab-cluster-nodegroup-worknodes-1"
2023-07-25 19:39:11 [ℹ]  waiting for the control plane to become ready
2023-07-25 19:39:11 [✔]  saved kubeconfig as "/home/ec2-user/.kube/config"
2023-07-25 19:39:11 [ℹ]  no tasks
2023-07-25 19:39:11 [✔]  all EKS cluster resources for "eks-lab-cluster" have been created
2023-07-25 19:39:11 [ℹ]  nodegroup "worknodes-1" has 2 node(s)
2023-07-25 19:39:11 [ℹ]  node "ip-192-168-15-26.us-west-2.compute.internal" is ready
2023-07-25 19:39:11 [ℹ]  node "ip-192-168-82-0.us-west-2.compute.internal" is ready
2023-07-25 19:39:11 [ℹ]  waiting for at least 1 node(s) to become ready in "worknodes-1"
2023-07-25 19:39:11 [ℹ]  nodegroup "worknodes-1" has 2 node(s)
2023-07-25 19:39:11 [ℹ]  node "ip-192-168-15-26.us-west-2.compute.internal" is ready
2023-07-25 19:39:11 [ℹ]  node "ip-192-168-82-0.us-west-2.compute.internal" is ready
2023-10-12 16:07:48 [✔]  EKS cluster "eks-lab-cluster" in "us-west-2" region is ready

이 명령을 실행하면 Amazon EKS 제어 영역과 해당 제어 영역이 관리하는 두 개의 작업자 노드를 포함하는 Amazon EKS 클러스터가 생성됩니다. 이 명령의 실행이 완료되는 동안 다음 태스크를 계속 진행할 수 있습니다.

클러스터를 생성하는 데 15~20분이 걸립니다.

주의: 실습 중에 다음 메시지 중 하나가 표시될 수 있습니다.

• EKS 클러스터에서 kubectl을 사용할 수 없음(‘kubectl 버전’ 확인): 경고: 이 버전 정보는 더 이상 사용되지 않으며 kubectl version --short의 출력으로 대체됩니다.
• 서버에 연결할 수 없음: 자격 증명 가져오기: stdout 디코딩: ‘ExecCredential’ 유형이 ‘pkg/client/auth/exec/exec.go:62’ 체계의 ‘client.authentication.k8s.io/v1alpha1’ 버전에 등록되어 있지 않습니다.
• EKS 클러스터에서 Kubernetes 버전 가져오기:  실행 오류: 종료 상태 1(‘kubectl 버전’ 확인)
• kubectl version

중간에 빨간색으로 버전 일치하지 않는다고 에러 나도, 무시하고 진행하면 된다

• 단지 버전 불일치로 나오는 에러이다.

aws eks update-kubeconfig --name eks-lab-cluster --region ${AWS_DEFAULT_REGION}

예상 출력

 

******************************
**** This is OUTPUT ONLY. ****
******************************

Added new context arn:aws:eks:us-west-2:638489295426:cluster/eks-lab-cluster to /home/ec2-user/.kube/config