Containerization has become the standard for modern application development, and Kubernetes is the undisputed leader for orchestrating these containers. But managing a raw Kubernetes cluster can be a daunting, complex, and time-consuming task. Enter Amazon Elastic Kubernetes Service (EKS), a managed service that takes the heavy lifting out of running Kubernetes on AWS. EKS automates the management of the Kubernetes control plane, allowing you to focus on deploying, managing, and scaling your containerized applications without worrying about the underlying infrastructure.
This article will be your go-to resource for all things EKS. We'll explore its core features, understand its architecture, and compare it to other services. By the end, you'll be able to confidently design and deploy scalable applications on EKS, leveraging the full power of Kubernetes with the reliability and security of AWS.
1. What is Amazon EKS?
Amazon EKS is a managed service that helps you run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes. EKS is an official Kubernetes conformant service, meaning any application that runs on a standard Kubernetes environment will run seamlessly on EKS. It provides the Kubernetes control plane for you, a highly available and scalable cluster that manages your containers. This includes the API server, scheduler, and etcd. You are responsible for the worker nodes—the EC2 instances where your containers actually run.
2. Key Features of Amazon EKS
EKS combines the power of Kubernetes with the robust features of the AWS ecosystem.
Managed Kubernetes Control Plane: AWS provides and manages a highly available, multi-AZ Kubernetes control plane.
7 It automatically handles patching, version upgrades, and security of the master nodes.Security and Compliance: EKS integrates with AWS IAM for authentication and authorization. It is also certified for various compliance standards, including SOC, ISO, and PCI DSS.
Scalability: EKS integrates with Amazon EC2 for worker nodes, allowing you to automatically scale your cluster up or down based on traffic. You can use the Kubernetes Cluster Autoscaler or AWS Auto Scaling groups.
Networking: EKS uses the Amazon VPC CNI plugin to assign each pod its own IP address from your VPC's subnet, enabling direct communication between pods and other AWS services.
Integration with AWS Services: EKS seamlessly integrates with other AWS services, such as Amazon CloudWatch for monitoring, AWS Fargate for serverless compute, and Amazon ECR for container image management.
Logging and Monitoring: EKS provides control plane logs through Amazon CloudWatch, giving you visibility into API calls, scheduler events, and more.
3. Internal Architecture of Amazon EKS
Understanding the architecture of EKS is key to designing a reliable and scalable container platform.
Managed Control Plane: The EKS control plane is a managed service that runs in an account owned by AWS.
13 It is a highly available and fault-tolerant cluster that spans multiple Availability Zones. This control plane consists of the API Server, Scheduler, Controller Manager, and etcd, which stores the state of your cluster.15 Worker Nodes: These are the EC2 instances that you provision and manage. The worker nodes run the kubelet and container runtime (e.g., containerd) to execute your containers. They join the EKS control plane and are where your applications are actually deployed.
Networking: The VPC CNI plugin is a crucial component that runs on the worker nodes. It allows pods to be assigned IP addresses from the VPC, making it easy to integrate with other VPC resources like databases or load balancers.
AWS Load Balancers: EKS integrates with the AWS Load Balancer Controller to automatically provision Application Load Balancers (ALBs) or Network Load Balancers (NLBs) to expose your services to the internet.
4. Benefits of Amazon EKS and its Difference from AWS Fargate
EKS provides a powerful, managed Kubernetes solution with a clear set of benefits.
Operational Simplicity: You no longer need to manage the complexity of the Kubernetes control plane. AWS handles patching, upgrades, and high availability, saving you significant time and resources.
Cost Efficiency: You only pay for the EC2 instances (worker nodes) and a nominal hourly fee for the managed control plane, making it cost-effective for large-scale deployments.
Flexibility: EKS gives you full control over your worker nodes, allowing you to choose the instance type, auto-scaling policy, and security group that best fits your needs.
EKS vs. AWS Fargate
While both EKS and Fargate are used for running containers, they serve different purposes.
| Feature | Amazon EKS | AWS Fargate |
| Control | You manage the worker nodes (EC2 instances). | AWS manages the underlying infrastructure. You only provide the container. |
| Cost Model | Pay for EC2 instances and the EKS control plane fee. | Pay for vCPU and memory usage per second. |
| Use Case | Ideal for applications that need fine-grained control over the EC2 instance, require custom software on the host, or have predictable, steady workloads. | Perfect for applications that don't need control over the underlying server and have unpredictable, spiky traffic. It's a true serverless compute for containers. |
| Simplicity | Requires some knowledge of Kubernetes and EC2 management. | Extremely simple; abstracts away all server management. |
5. Compare Amazon EKS with Azure and Google Cloud Services
The major cloud providers all offer managed Kubernetes services. Here's a quick comparison.
| Feature | Amazon EKS | Azure Kubernetes Service (AKS) | Google Kubernetes Engine (GKE) |
| Management | AWS manages the control plane. You manage the worker nodes. | Azure manages the control plane. You manage the worker nodes. | Google manages both the control plane and worker nodes (in Autopilot mode). |
| Integration | Deep integration with AWS services like IAM, VPC, and CloudWatch. | Deep integration with Azure Active Directory and other Azure services. | Deep integration with Google's network and services, known for its strong auto-scaling features. |
| Pricing | Control plane fee + EC2 costs. | Control plane is free for standard tier. You pay for the underlying VMs. | Control plane is free. You pay for the underlying VMs. Autopilot mode charges based on resource usage. |
| Market Share | EKS is a market leader and widely adopted by enterprises. | Strong competitor, especially for companies in the Microsoft ecosystem. | GKE is the original managed Kubernetes service and is known for its technical leadership. |
6. Hard Limits and Misconceptions on Amazon EKS
Misconception: EKS is a true serverless service. This is only true if you run EKS on AWS Fargate. If you run EKS with EC2 worker nodes, you are still responsible for managing and scaling the instances, including their patching.
Hard Limit: Cluster Count: You are limited to a certain number of EKS clusters per AWS region. This is a soft limit that can be increased by contacting AWS support.
Misconception: EKS automatically scales everything. EKS does not automatically scale your worker nodes out-of-the-box. You must configure the Cluster Autoscaler or AWS Auto Scaling Groups to do this.
Misconception: You can use any Kubernetes version. EKS supports specific versions of Kubernetes, and you are responsible for updating your cluster to a new supported version when it becomes available.
7. Top 10 Real-World Use Cases for Amazon EKS
Microservices: EKS is the perfect platform for running microservices architectures, as it provides a robust way to deploy, scale, and manage a large number of independent services.
Web and Mobile Applications: Powers high-traffic web apps by providing a scalable and highly available platform for containerized web servers and APIs.
CI/CD Pipelines: EKS can be a key component in a modern CI/CD pipeline, used to automatically deploy new application versions to a production environment.
Gaming: Manages multiplayer game servers, handling a large number of concurrent players and dynamic scaling based on demand.
Machine Learning: Deploys and manages machine learning models as services, with EKS providing the compute and scalability required for inference.
26 Batch Processing: Runs large-scale, distributed batch processing jobs, taking advantage of Kubernetes's job scheduling capabilities.
Data Streaming: Deploys and manages streaming applications with tools like Apache Kafka or Flink.
Internal Business Applications: Used to modernize legacy applications by containerizing them and deploying them on a scalable platform.
IoT: Manages containerized applications for ingesting and processing data from millions of IoT devices.
Hybrid Cloud: EKS Anywhere extends the EKS platform to on-premises environments, allowing for a consistent Kubernetes experience across hybrid clouds.
8. Design Dockerizing and Deploying a Web Application on Amazon EKS Cluster
Here's a step-by-step guide to dockerizing a simple web application and deploying it on an EKS cluster.
Step 1: Write a Simple Web App
Create a simple Python Flask web server in a file named app.py.
# app.py
from flask import Flask
app = Flask(__name__)
@app.route('/')
def hello_world():
return 'Hello, EKS! This is a containerized web app.'
if __name__ == '__main__':
app.run(host='0.0.0.0', port=5000)
Step 2: Create a Dockerfile
Create a Dockerfile to containerize your application.
# Dockerfile
FROM python:3.9-slim
WORKDIR /app
COPY . .
RUN pip install Flask
EXPOSE 5000
CMD ["python", "app.py"]
Step 3: Build and Push the Docker Image
Build the Docker image and push it to Amazon ECR (Elastic Container Registry).
# Authenticate Docker to ECR
aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin <YOUR_ECR_URI>
# Build the image
docker build -t my-web-app .
# Tag and push the image to ECR
docker tag my-web-app:latest <YOUR_ECR_URI>/my-web-app:latest
docker push <YOUR_ECR_URI>/my-web-app:latest
Step 4: Create a Kubernetes Deployment Manifest
Create a file named deployment.yaml to define your deployment and service.
# deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-web-app-deployment
labels:
app: my-web-app
spec:
replicas: 3
selector:
matchLabels:
app: my-web-app
template:
metadata:
labels:
app: my-web-app
spec:
containers:
- name: my-web-app
image: <YOUR_ECR_URI>/my-web-app:latest
ports:
- containerPort: 5000
---
apiVersion: v1
kind: Service
metadata:
name: my-web-app-service
annotations:
service.beta.kubernetes.io/aws-load-balancer-type: external
service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
spec:
selector:
app: my-web-app
type: LoadBalancer
ports:
- protocol: TCP
port: 80
targetPort: 5000
Step 5: Apply the Manifest to Your EKS Cluster
Ensure your kubectl is configured to connect to your EKS cluster.
kubectl apply -f deployment.yaml
The kubectl apply command will create a Deployment that manages 3 replicas of your application and a LoadBalancer Service that provisions an AWS Network Load Balancer (NLB) to expose your app to the internet. After a few minutes, you can get the DNS name of the load balancer and access your application.
9. Conclusion
Amazon EKS is the ideal service for organizations that want to leverage the power of Kubernetes without the operational burden of managing the control plane. It provides a secure, scalable, and highly available platform that deeply integrates with the AWS ecosystem. By understanding its architecture and best practices, you can build and deploy modern, containerized applications with confidence, freeing up your team to focus on what matters most: innovation.
Ready to take your container strategy to the next level? Start building with Amazon EKS today.
10. Recommended AWS Blog Links on Amazon EKS
AWS Containers Blog:
https://aws.amazon.com/blogs/containers/ EKS Best Practices Guide:
https://aws.github.io/aws-eks-best-practices/ EKS Workshops:
https://www.eksworkshop.com/
11. Good Amazon EKS Knowledge Practice Questions
What is the primary responsibility of AWS in managing an EKS cluster?
a) Managing both the control plane and worker nodes.
b) Managing only the worker nodes.
c) Managing the control plane, including API Server, scheduler, and etcd.
d) Managing only the container images.
Answer: c) Managing the control plane, including API Server, scheduler, and etcd. AWS provides the managed control plane for you.
Which AWS service is used to assign a VPC IP address to each pod in an EKS cluster?
a) AWS Fargate
b) AWS CloudFormation
c) Amazon VPC CNI plugin
d) Amazon EC2
Answer: c) Amazon VPC CNI plugin. This is a crucial component that allows pods to communicate directly with other VPC resources.
What is the main benefit of using EKS with Fargate?
a) It provides a cheaper way to run containers.
b) It gives you more control over the underlying EC2 instances.36
c) It abstracts away the need to manage worker nodes (EC2 instances).37
d) It allows you to run any type of container.
Answer: c) It abstracts away the need to manage worker nodes (EC2 instances). Fargate provides a serverless compute engine for containers.
How can you expose a service running in an EKS cluster to the internet?
a) By creating a Service of type NodePort.
b) By creating a Service of type LoadBalancer or using an Ingress controller.
c) By manually assigning an Elastic IP address to a pod.
d) By using a Service of type ClusterIP.
Answer: b) By creating a Service of type
LoadBalanceror using an Ingress controller. This will automatically provision an AWS Load Balancer.
Which of the following is a key responsibility of the user when running EKS with EC2 worker nodes?
a) Upgrading the Kubernetes control plane.
b) Patching the control plane's operating system.
c) Scaling the worker nodes to handle load.
d) Ensuring the etcd database is backed up.
Answer: c) Scaling the worker nodes to handle load. You are responsible for managing the EC2 instances.
What is the purpose of the kubelet agent on an EKS worker node?
a) To manage container images.
b) To run containers and register the node with the control plane.
c) To manage the cluster's networking.
d) To manage secrets and configurations.
Answer: b) To run containers and register the node with the control plane. The kubelet is the primary agent that communicates with the control plane.
What does a Kubernetes Deployment object do?
a) It defines a network service.
b) It manages the desired state of a set of replica pods.
c) It stores secrets and configuration data.
d) It defines the worker nodes.
Answer: b) It manages the desired state of a set of replica pods.
Which AWS service is commonly used as a private container registry with EKS?
a) Amazon S3
b) Amazon EC2
c) Amazon ECR (Elastic Container Registry)
d) Amazon RDS
Answer: c) Amazon ECR (Elastic Container Registry). ECR is a fully managed Docker container registry that integrates seamlessly with EKS.
How can you provide fine-grained access control to EKS resources based on IAM users and roles?
a) By using a Service Account.
b) By configuring a Security Group.
c) By using the AWS ConfigMap aws-auth.
d) By using an Ingress Controller.
Answer: c) By using the AWS
ConfigMapaws-auth. ThisConfigMapmaps IAM roles and users to Kubernetes roles.
What is a "pod" in Kubernetes?
a) A single Docker container.
b) The smallest and simplest unit of an application in Kubernetes.
c) A group of worker nodes.
d) A network service.
Answer: b) The smallest and simplest unit of an application in Kubernetes. A pod can contain one or more containers.
Which of the following is NOT part of the EKS managed control plane?
a) API Server
b) etcd
c) Worker Nodes
d) Scheduler
Answer: c) Worker Nodes. You are responsible for provisioning and managing the worker nodes.
Which service would you use to automatically scale your EKS worker nodes based on CPU usage?
a) Kubernetes Horizontal Pod Autoscaler (HPA)49
b) AWS Auto Scaling Group
c) AWS CloudWatch
d) AWS Lambda
Answer: b) AWS Auto Scaling Group. The Kubernetes Cluster Autoscaler works in conjunction with AWS Auto Scaling Groups to scale worker nodes.
What is a "Service" in Kubernetes?
a) A way to manage persistent storage.
b) An abstract way to expose an application running on a set of pods.
c) A tool for managing container images.
d) A way to provision new pods.
Answer: b) An abstract way to expose an application running on a set of pods.
How does EKS handle network security for your worker nodes?
a) It automatically creates a new VPC.
b) It uses AWS Security Groups to control inbound and outbound traffic.51
c) It uses NACLs.
d) It does not provide any network security.
Answer: b) It uses AWS Security Groups to control inbound and outbound traffic. You configure the security groups for your worker nodes.
Which Kubernetes object is best for running a one-off, non-reoccurring task?
a) Deployment
b) Service
c) Pod
d) Job
Answer: d) Job. A Job creates one or more pods and ensures that a specified number of them terminate successfully.
What is the purpose of the Kubernetes Scheduler?
a) To manage the state of the cluster.
b) To store cluster configuration.
c) To manage network services.
d) To assign pods to worker nodes.
Answer: d) To assign pods to worker nodes. The scheduler watches for new pods and assigns them to a healthy worker node.
Which of the following would you use to provision and manage EKS worker nodes?
a) A single EC2 instance.
b) An AWS Auto Scaling Group.
c) A Kubernetes Deployment.
d) A Lambda function.
Answer: b) An AWS Auto Scaling Group. This provides a scalable and highly available way to manage your worker nodes.
What does an Ingress controller do in Kubernetes?
a) It provisions a load balancer to expose a service.
b) It manages the ingress of network traffic to multiple services from a single entry point.
c) It automatically scales your pods.
d) It manages secrets and configurations.
Answer: b) It manages the ingress of network traffic to multiple services from a single entry point.
How do you secure container images in EKS?
a) EKS automatically scans all images.
b) By storing images in a private registry like ECR and using IAM roles to control access.
c) By using a public registry.
d) By not using any registry.
Answer: b) By storing images in a private registry like ECR and using IAM roles to control access.
57
Which of the following is true about EKS control plane logs?
a) They are automatically sent to S3.
b) They are managed by the user.
c) They can be enabled and sent to Amazon CloudWatch.
d) They are not available to the user.
Answer: c) They can be enabled and sent to Amazon CloudWatch. This provides valuable insights into cluster operations.
What is a ConfigMap in Kubernetes?
a) A way to store sensitive information.
b) A way to store non-sensitive configuration data for an application.
c) A way to manage a pod's network settings.
d) A way to store the state of the cluster.
Answer: b) A way to store non-sensitive configuration data for an application.
What is the purpose of a Namespace in Kubernetes?
a) To define a new user.
b) To create a virtual network.
c) To create a virtual cluster to isolate resources.
d) To define a service.
Answer: c) To create a virtual cluster to isolate resources. Namespaces are a way to organize and logically isolate resources within a single cluster.
What is a "ReplicaSet" in Kubernetes?
a) An object that manages a set of replicas for a pod.
b) A service that manages stateful applications.
c) A way to expose an application.
d) A way to manage a one-off task.
Answer: a) An object that manages a set of replicas for a pod. A Deployment internally uses a ReplicaSet to manage its pods.
Which AWS service would you use for persistent storage for a stateful application on EKS?
a) Amazon S3
b) Amazon EBS (Elastic Block Store) with the CSI driver
c) Amazon RDS
d) AWS CloudFormation
Answer: b) Amazon EBS (Elastic Block Store) with the CSI driver. EBS volumes can be provisioned and attached to pods for persistent storage.
How does EKS authenticate IAM users to a Kubernetes cluster?
a) By using SSH keys.
b) By mapping IAM roles and users to Kubernetes RBAC roles via the aws-auth ConfigMap.
c) By using a separate authentication service.
d) EKS does not support IAM authentication.
Answer: b) By mapping IAM roles and users to Kubernetes RBAC roles via the
aws-authConfigMap.
Which of the following is true about EKS clusters?
a) They can span multiple AWS regions.
b) They are deployed within a single AWS region.
c) They are limited to a single Availability Zone.
d) They do not use a VPC.
Answer: b) They are deployed within a single AWS region. The managed control plane spans multiple AZs within that region.
What is the purpose of the aws-auth ConfigMap?
a) To manage application-level configuration.
b) To define a Kubernetes service.
c) To map AWS IAM users/roles to Kubernetes users/groups for authentication.
d) To manage secrets.
Answer: c) To map AWS IAM users/roles to Kubernetes users/groups for authentication.
How can you ensure that your EKS worker nodes are automatically updated with security patches?
a) AWS automatically patches worker nodes.
b) You must manually SSH into each node and apply patches.
c) By using a tool like AWS Systems Manager to automate patching.
d) EKS worker nodes are not updated.
Answer: c) By using a tool like AWS Systems Manager to automate patching. You are responsible for patching your EC2 worker nodes.
What is a "Helm chart" in the context of EKS?
a) A monitoring dashboard for EKS.
b) A package manager for Kubernetes applications.
c) A tool for managing EKS clusters.
d) A type of Kubernetes service.
Answer: b) A package manager for Kubernetes applications. Helm simplifies the deployment of complex applications on Kubernetes.
What is a DaemonSet used for in Kubernetes?
a) To run a single pod in a cluster.
b) To ensure that a copy of a pod runs on every worker node.63
c) To manage a set of stateful replicas.
d) To run a one-off task.
Answer: b) To ensure that a copy of a pod runs on every worker node.
64 This is often used for logging agents or monitoring tools.
Which of the following is a key advantage of EKS over a self-managed Kubernetes cluster on EC2?
a) EKS is completely free.
b) EKS provides full root access to the control plane.
c) You don't have to worry about managing the control plane.
d) EKS is only compatible with a single container runtime.
Answer: c) You don't have to worry about managing the control plane.
How does EKS handle container networking with the VPC CNI plugin?
a) It uses an overlay network to assign a virtual IP to each pod.65
b) It assigns a private IP address from your VPC to each pod.
c) It assigns a public IP address to each pod.66
d) It routes all traffic through a single NAT Gateway.
Answer: b) It assigns a private IP address from your VPC to each pod.
What is the purpose of the etcd component in the EKS control plane?
a) To manage the network.
b) To schedule pods.
c) To serve as the cluster's database, storing its state and configuration.
d) To handle container images.
Answer: c) To serve as the cluster's database, storing its state and configuration.
Which AWS service is commonly used with EKS to store and manage secrets?
a) Amazon S3
b) AWS Secrets Manager
c) Amazon DynamoDB
d) AWS CloudTrail
Answer: b) AWS Secrets Manager. Secrets Manager can integrate with EKS to provide secure, managed storage for secrets and credentials.
What is a StatefulSet used for?
a) To manage stateless applications.
b) To manage a set of replicas with stable network identifiers and persistent storage.
c) To manage a one-off task.
d) To manage container images.
Answer: b) To manage a set of replicas with stable network identifiers and persistent storage.
When using EKS, which tool is commonly used to deploy Kubernetes applications from a manifest file?
a) Docker
b) Kubectl67
c) EKSCTL
d) AWS CLI
Answer: b) Kubectl.
kubectlis the standard command-line tool for interacting with a Kubernetes cluster.
What is the benefit of running EKS on Fargate?
a) It is always cheaper than using EC2 worker nodes.
b) You have complete control over the underlying instances.
c) You don't need to provision or manage any worker nodes.68
d) It provides full root access to the OS.
Answer: c) You don't need to provision or manage any worker nodes.
69
Which of the following is the best practice for isolating different environments (e.g., Dev, Staging, Prod) within a single EKS cluster?
a) Use different worker nodes for each environment.
b) Use different namespaces for each environment.
c) Use different EKS clusters for each environment.
d) Use a different VPC for each environment.
Answer: b) Use different namespaces for each environment. This provides a logical isolation layer within the same cluster.
How can you get the logs from your application running inside an EKS pod?
a) By using kubectl logs.
b) By SSHing into the worker node.
c) By checking the S3 logs.
d) You cannot get the logs.
Answer: a) By using
kubectl logs. This is the standard way to retrieve container logs from a pod.
What is the purpose of the service.beta.kubernetes.io/aws-load-balancer-type annotation?
a) To specify the type of load balancer to be provisioned (e.g., NLB or ALB).
b) To specify the type of service.
c) To define the worker node type.
d) To manage the pods.
Answer: a) To specify the type of load balancer to be provisioned (e.g., NLB or ALB).
Which of the following is a common method for deploying an EKS cluster with a single command?
a) kubectl create cluster
b) eksctl
c) aws eks create-cluster
d) docker run
Answer: b)
eksctl.eksctlis a simple CLI tool for creating and managing EKS clusters.
What is the purpose of a Kubernetes Ingress object?
a) To expose a single service.
b) To manage external access to services in a cluster, typically HTTP/HTTPS.
c) To manage internal pod communication.
d) To manage a database.
Answer: b) To manage external access to services in a cluster, typically HTTP/HTTPS.
What is the primary role of the Kubernetes API Server?
a) To manage the worker nodes.
b) To expose the Kubernetes API for communication.
c) To store cluster state.
d) To manage network services.
Answer: b) To expose the Kubernetes API for communication.
Which component would you use to provide a custom DNS name for your EKS service?
a) A Service of type LoadBalancer.
b) An Ingress Controller.
c) AWS CloudFormation.
d) The Kubernetes API Server.
Answer: b) An Ingress Controller. An Ingress Controller can provision an ALB and manage DNS routing for multiple services.
What is a "container runtime" on an EKS worker node?
a) The same as Docker.
b) The software that runs containers (e.g., containerd).
c) A Kubernetes service.
d) The operating system of the worker node.
Answer: b) The software that runs containers (e.g., containerd).
What is the ServiceAccount in Kubernetes used for?
a) To manage human user accounts.
b) To provide an identity for processes that run in a Pod.
c) To manage external services.
d) To store secrets.
Answer: b) To provide an identity for processes that run in a Pod.
What is a ClusterIP service type?
a) It exposes the service on a private IP address only accessible within the cluster.
b) It exposes the service on a public IP address.
c) It exposes the service on a specific port of each worker node.
d) It exposes the service on a public load balancer.
Answer: a) It exposes the service on a private IP address only accessible within the cluster.
Which of the following is the most secure method for exposing a service on EKS?
a) Using a NodePort.
b) Using a LoadBalancer with a public schema.
c) Using an Ingress controller with a WAF.
d) Exposing the service directly to the internet.
Answer: c) Using an Ingress controller with a WAF. This provides an additional layer of security against web attacks.
What is the purpose of the AWS Load Balancer Controller for EKS?
a) To provision a Load Balancer for a Service.
b) To provision worker nodes.
c) To manage DNS.
d) To scale pods.
Answer: a) To provision a Load Balancer for a Service.
What is the primary advantage of using eksctl over the AWS CLI to create an EKS cluster?
a) eksctl is faster.
b) eksctl automates the creation of a cluster and its worker nodes with a single command.
c) eksctl is the only supported tool.
d) The AWS CLI cannot create EKS clusters.
Answer: b)
eksctlautomates the creation of a cluster and its worker nodes with a single command.
No comments:
Post a Comment