Compute - EKS (Elastic Container Service for Kubernetes

Question 1

What is Kubernetes?

Answer 1

• Kubernetes is an open-source container orchestration tool.
• It automates the deployment, scaling, and operation of containerized applications.
• It is container-runtime agnostic and supports rocket and docker containers.

Question 2

What is EKS?

Answer 2

• EKS stands for Elastic Container Service for Kubernetes.
• It is a managed service by AWS for running Kubernetes on AWS infrastructure.
• AWS takes care of provisioning and managing the Kubernetes control plane, while the user manages the worker nodes.

Question 3

What is the Kubernetes control plane?

Answer 3

• The control plane includes APIs, kubelet processes, and the Kubernetes Master.
• It facilitates communication between Kubernetes and clusters.
• AWS is responsible for provisioning, scaling, and managing the control plane in EKS.

Question 4

What are worker nodes in EKS?

Answer 4

• Worker nodes are EC2 instances that run containers managed by the Kubernetes control plane.
• They are responsible for executing containerized applications.
• Users are responsible for provisioning and managing the worker nodes in EKS.

Question 5

What is required to start using EKS?

Answer 5

• Create an EKS Service Role with the necessary permissions.
• Create an EKS Cluster VPC using AWS CloudFormation.
• Install kubectl and AWS-IAM-Authenticator.
• Create the EKS cluster using the EKS console.
• Configure kubectl for the EKS cluster.
• Provision and configure worker nodes using CloudFormation.
• Configure the worker nodes to join the EKS cluster.

Question 6

What is the purpose of the IAM service-role in EKS?

Answer 6

• The IAM service-role allows EKS to provision and configure specific resources.
• It needs the AmazonEKSServicePolicy and AmazonEKSClusterPolicy permissions policies attached.
• The role only needs to be created once and can be used for multiple EKS clusters.

Question 7

How can worker nodes be configured to join the EKS cluster?

Answer 7

• Download the configuration map (aws-auth-cm.yaml) and edit it.
• Replace the “< ARN of instance role (not instance profile)>” with the NodeInstanceRole value.
• Apply the configuration map to the cluster.