Scribd
Upload
53 views12 pages

CH 02

The document summarizes a session on using AWS EKS. It discusses using the eksctl tool to launch EKS clusters from YAML files in a declarative way. Nodegroups manage nodes and provide fault tolerance. Images are used to bundle software and deploy containers/pods. The master monitors pods through kubelet. VPCs are created with subnets and IP ranges to provide network access. EKS uses an internal load balancer while exposing services externally uses type LoadBalancer.

Uploaded by

sameo13
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
53 views12 pages

CH 02

The document summarizes a session on using AWS EKS. It discusses using the eksctl tool to launch EKS clusters from YAML files in a declarative way. Nodegroups manage nodes and provide fault tolerance. Images are used to bundle software and deploy containers/pods. The master monitors pods through kubelet. VPCs are created with subnets and IP ranges to provide network access. EKS uses an internal load balancer while exposing services externally uses type LoadBalancer.

Uploaded by

sameo13
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

[AWS]

AWS Session
Summary - 19-3-2023

• If we want to use EKS we use eksctl tool:


1. CLI
2. Code (YAML)
• Nodegroup will manage the nodes. Nodegroup is managed by AWS. It will
help in disaster recovery.
• ssm here is similar as ssh. Ssh-keygen creates public and private key.
• YAML: It is a generic way of formatting/providing information. It cab be
represented in the form of key-value pair. Equal spacing given in yaml file
is called indentation.
• Nodegroup is one array which is in the form of hashes and dictionary.
• If we want to launch Kubernetes cluster using eksctl tool with the help of
yml file then it means sending instruction which is called a declarative
language. So yaml is a way to declare what we are declaring.

PRACTICAL

pg. 1
[AWS]

Now creating the cluster.

pg. 2
[AWS]

Cluster launched successfully.

pg. 3
[AWS]

pg. 4
[AWS]

pg. 5
[AWS]

• If we want to launch OS, server,app then that entire software we bundle in


one box or software called Image and image in container world is called
container image.
• We can create own images or if we want pre created image we can get from
hub.docker.com

• If we want to launch app/container/pod with the help of image we call it


as a deployment in k8s.
• Setup which k8s gives is highly resilient and fault tolerant.

pg. 6
[AWS]

• Master keeps on monitoring the pod because there is a program running in


worker nodes who communicates with the master, the program is known
as kubelet. This is also managed by EKS.

pg. 7
[AWS]

Now creating a deployment using image httpd

Able to see the content.

pg. 8
[AWS]

To check deployments use kubectl get deployment

• AWS has its own personal plugin called VPC Pugin for k8s cluster. So
whenever we launch a cluster with EKS it launches VPC. Every VPC
belongs to a subnet and every subnet gives a range of IP address. Every
subnet has a personal range of network.

pg. 9
[AWS]

• AWS has a service called internet gateway which allows anybody entire
that IP range to access the app. eksctl also creates the internet gateway.
• EKS has its own internal Load balancer. LB in Kubernetes is called a
svc(service) that is created by a program which have some limit.
• In EKS load balancer is Elastic load balancer-ELB.
Other types of LB in AWS are:
1. NLB- Network load balancer (gives high speed)
2. ALB- Application load balancer (gives ingress setup)
3. GLB- Gateway load balancer (Advanced setup that manages traffic,
encrypt traffic, monitoring)
• For exposing a service we use kubectl expose deployment myweb --
name=mylbsvc --type=LoadBalancer –port 80
Here expose means anybody can able to see the application over the internet.

pg. 10
[AWS]

Now we can able to access the webpage successfully.

pg. 11
[AWS]

pg. 12

You might also like