The tutorial demonstrates creating an Amazon EKS cluster using eksctl, configuring node groups, and deploying applications with Helm. It covers managing Kubernetes secrets, scaling node groups, setting up the AWS Load Balancer Controller for ingress, and testing external connectivity via Postman.
Length 12:29
Captions English (Generated), Spanish (Auto-translated), French (Auto-translated), Korean (Auto-translated), Portuguese (Auto-translated), Vietnamese (Auto-translated) #kubernetes #eks #aws #eksctl #helm #cloudformation #load balancer #iam #deployment #infrastructure
0:00 Okay, so to create our EKS cluster on AWS, we're gonna use 0:04 a command line tool called eksctl, which is the official 0:08 CLI for Amazon EKS, and will allow us to easily 0:12 create and manage our clusters from the command line. 0:15 So to get started, let's click on the Introduction page, and 0:19 we are at eksctl.io. 0:22 Click on Introduction, and then on the right here, let's click on 0:25 Installation to find out how we can install eksctl. 0:30 So you can see for your operating system, we have different installation commands. 0:34 Here is for Windows and for Unix. 0:37 So go ahead and copy and paste these commands into your 0:40 terminal to make sure you 0:41 have eksctl, it, properly installed. 0:45 So after you have it installed, you should be able to go to your command 0:48 line and 0:48 run eksctl get clusters, and this is gonna use 0:52 the default AWS credentials we set up at the beginning. 0:57 We wanna go ahead and define a new cluster config file in 1:00 our project that 1:01 will define how our cluster is created. 1:04 So if we go back to the documentation and go to the homepage, we can 1:08 scroll down until we find a default cluster.yaml file. 1:12 Let's go ahead and copy this, and then we can go back to our root 1:15 project 1:16 and create a new cluster.yaml, and I'll paste in this 1:20 cluster config, 1:22 where we can change the name to be called sleeper, and I'm gonna 1:26 change the region to be closest to me, which is 1:28 us-east-1. Feel, feel free to use whichever region you 1:32 would like. 1:33 And then importantly, we have different node groups defined, 1:36 and this is gonna be 1:37 the nodes we have available to run our workloads. 1:40 In our case, we only want to run one node group. 1:44 So we can call it NG1, and we wanna change the instance type
The rest of the transcript is for members.
Sign in 