Key Points
-
AWS EKS is a service that we can use to set up Kubernetes.
-
The
deployment.yaml
file is used to specify how our pods should be created. - The
service.yaml
file is used to specify how our pods are exposed.
deployment.yaml
apiVersion: apps/v1 kind: Deployment metadata: name: my-app labels: app: my-app spec: replicas: 2 selector: matchLabels: app: my-app template: metadata: labels: app: my-app spec: containers: - name: simple-node image: YOUR_DOCKER_HUB/simple-node ports: - containerPort: 80
service.yaml
apiVersion: v1 kind: Service metadata: name: my-app labels: run: my-app spec: ports: - port: 80 protocol: TCP selector: run: my-app
Creating a Kubernetes Cluster on AWS
Creating an EKS Cluster
- Create cluster in EKS
- Create and specify role for Kubernetes cluster
- Enable public access
Creating a Node Group
- Add Node Group in the newly-created cluster
- Create and specify role for IAM role for node group
- Create and specify SSH key for node group
- Set instance type to
t3.micro
for cost-savings as we learn how to use Kubernetes - Specify desired number of nodes
![[AWS] Kubernetes on AWS_sed](https://s2.51cto.com/images/blog/202107/31/88c4d3c0fc1519c490ea9fbec7fbf24c.jpeg?x-oss-process=image/watermark,size_16,text_QDUxQ1RP5Y2a5a6i,color_FFFFFF,t_30,g_se,x_10,y_10,shadow_20,type_ZmFuZ3poZW5naGVpdGk=/resize,m_fixed,w_1184)
Docker images are loaded from the container registry into Kubernetes pods. Access to the pods are exposed to consumers through a service.