eksctl create cluster success log

❯ eksctl create cluster --config-file eks/cluster-1.25.yaml
2023-04-08 14:39:42 [ℹ]  eksctl version 0.134.0
2023-04-08 14:39:42 [ℹ]  using region us-west-2
2023-04-08 14:39:43 [ℹ]  skipping us-west-2d from selection because it doesn't support the following instance type(s): t2.small
2023-04-08 14:39:43 [ℹ]  setting availability zones to [us-west-2c us-west-2a us-west-2b]
2023-04-08 14:39:43 [ℹ]  subnets for us-west-2c - public:192.168.0.0/19 private:192.168.96.0/19
2023-04-08 14:39:43 [ℹ]  subnets for us-west-2a - public:192.168.32.0/19 private:192.168.128.0/19
2023-04-08 14:39:43 [ℹ]  subnets for us-west-2b - public:192.168.64.0/19 private:192.168.160.0/19
2023-04-08 14:39:43 [ℹ]  nodegroup "timeworx-admin-ng-usw2" will use "" [AmazonLinux2/1.25]
2023-04-08 14:39:43 [ℹ]  using Kubernetes version 1.25
2023-04-08 14:39:43 [ℹ]  creating EKS cluster "timeworx-admin" in "us-west-2" region with managed nodes
2023-04-08 14:39:43 [ℹ]  1 nodegroup (timeworx-admin-ng-usw2) was included (based on the include/exclude rules)
2023-04-08 14:39:43 [ℹ]  will create a CloudFormation stack for cluster itself and 0 nodegroup stack(s)
2023-04-08 14:39:43 [ℹ]  will create a CloudFormation stack for cluster itself and 1 managed nodegroup stack(s)
2023-04-08 14:39:43 [ℹ]  if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --cluster=timeworx-admin'
2023-04-08 14:39:43 [ℹ]  Kubernetes API endpoint access will use default of {publicAccess=true, privateAccess=false} for cluster "timeworx-admin" in "us-west-2"
2023-04-08 14:39:43 [ℹ]  CloudWatch logging will not be enabled for cluster "timeworx-admin" in "us-west-2"
2023-04-08 14:39:43 [ℹ]  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=timeworx-admin'
2023-04-08 14:39:43 [ℹ]
2 sequential tasks: { create cluster control plane "timeworx-admin",
    2 sequential sub-tasks: {
        wait for control plane to become ready,
        create managed nodegroup "timeworx-admin-ng-usw2",
    }
}
2023-04-08 14:39:43 [ℹ]  building cluster stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:39:43 [ℹ]  deploying stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:40:13 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:40:44 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:41:44 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:42:44 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:43:44 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:44:44 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:45:44 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:46:45 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:47:45 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:48:45 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:49:45 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:50:45 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-cluster"
2023-04-08 14:52:47 [ℹ]  building managed nodegroup stack "eksctl-timeworx-admin-nodegroup-timeworx-admin-ng-usw2"
2023-04-08 14:52:48 [ℹ]  deploying stack "eksctl-timeworx-admin-nodegroup-timeworx-admin-ng-usw2"
2023-04-08 14:52:48 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-nodegroup-timeworx-admin-ng-usw2"
2023-04-08 14:53:18 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-nodegroup-timeworx-admin-ng-usw2"
2023-04-08 14:54:07 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-nodegroup-timeworx-admin-ng-usw2"
2023-04-08 14:55:26 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-nodegroup-timeworx-admin-ng-usw2"
2023-04-08 14:57:16 [ℹ]  waiting for CloudFormation stack "eksctl-timeworx-admin-nodegroup-timeworx-admin-ng-usw2"
2023-04-08 14:57:16 [ℹ]  waiting for the control plane to become ready
2023-04-08 14:57:17 [✔]  saved kubeconfig as "/Users/lizichen/.kube/config"
2023-04-08 14:57:17 [ℹ]  no tasks
2023-04-08 14:57:17 [✔]  all EKS cluster resources for "timeworx-admin" have been created
2023-04-08 14:57:17 [ℹ]  nodegroup "timeworx-admin-ng-usw2" has 3 node(s)
2023-04-08 14:57:17 [ℹ]  node "ip-192-168-17-61.us-west-2.compute.internal" is ready
2023-04-08 14:57:17 [ℹ]  node "ip-192-168-44-4.us-west-2.compute.internal" is ready
2023-04-08 14:57:17 [ℹ]  node "ip-192-168-67-15.us-west-2.compute.internal" is ready
2023-04-08 14:57:17 [ℹ]  waiting for at least 3 node(s) to become ready in "timeworx-admin-ng-usw2"
2023-04-08 14:57:17 [ℹ]  nodegroup "timeworx-admin-ng-usw2" has 3 node(s)
2023-04-08 14:57:17 [ℹ]  node "ip-192-168-17-61.us-west-2.compute.internal" is ready
2023-04-08 14:57:17 [ℹ]  node "ip-192-168-44-4.us-west-2.compute.internal" is ready
2023-04-08 14:57:17 [ℹ]  node "ip-192-168-67-15.us-west-2.compute.internal" is ready
2023-04-08 14:57:17 [ℹ]  kubectl command should work with "/Users/lizichen/.kube/config", try 'kubectl get nodes'
2023-04-08 14:57:17 [✔]  EKS cluster "timeworx-admin" in "us-west-2" region is ready