Exam2-Part2(EKS) Flashcards
1
Q
EKS Cluster Components
A
- EKS control plane
- EKS nodes
2
Q
EKS control plane
A
- It is made up of nodes that run the Kubernetes software (API server & ).
- Each cluster is single-tenant and unique, and runs on its own set of EC2 instances.
- Cluster control plane is provisioned across multiple AZs and fronted by an ELB Network Load Balancer.
- Uses AWS KMS to encrypt data stored by nodes and associated EBS volumes.
3
Q
EKS nodes
A
- A cluster consists of one or more EC2 nodes on which pods are scheduled.
- Connects to the cluster’s control plane via the API server endpoint.
4
Q
EKS supports two autoscaling products
A
- Cluster Autoscaler – uses AWS Auto Scaling groups.
- Karpenter – works directly with the Amazon EC2 Fleet.
5
Q
EKS control Plane Logs
A
By default, cluster control plane logs aren’t sent to CloudWatch Logs. In order to send logs for your cluster, you have to enable each log type individually.
6
Q
Amazon EKS Storage
A
Container Storage Interface (CSI) enables third-party storage providers to create and deploy plugins in Kubernetes that provide alternative storage systems without modifying the core Kubernetes code.
7
Q
Amazon EBS CSI driver
A
- The lifecycle of persistent volumes, such as EBS volumes, is handled by EKS clusters.
- To make calls to AWS APIs, the EBS CSI plugin requires IAM permissions.
- Although the Amazon EBS CSI controller can be run on Fargate, volumes cannot be mounted to Fargate pods.
- You can also manage the EBS CSI driver as an EKS add-on.
8
Q
Amazon EFS CSI driver
A
- EKS clusters manage the EFS file system lifecycle.
- Container images based on Windows are incompatible with the EFS CSI driver.
- Fargate nodes only support static provisioning.
- A pod running on Fargate automatically mounts an EFS file system.
9
Q
Amazon FSx for Lustre CSI driver
A
- EKS clusters can also manage the lifecycles of FSx file systems.
- Fargate does not support the Lustre CSI driver.
