Node groups (managed, self-managed, Fargate) in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a managed node group in AWS EKS?

A managed node group is a set of worker nodes in EKS that AWS automatically manages for you. AWS handles tasks like provisioning, updating, and scaling the nodes.

beginner

How does a self-managed node group differ from a managed node group?

A self-managed node group is where you manually create and manage the worker nodes yourself. You handle updates, scaling, and maintenance instead of AWS.

beginner

What is AWS Fargate in the context of EKS?

AWS Fargate lets you run containers without managing servers or nodes. It automatically provisions and scales compute resources for your pods.

beginner

Which node group type requires you to manage the underlying EC2 instances?

Self-managed node groups require you to manage the EC2 instances, including updates, scaling, and health checks.

beginner

What is a key benefit of using Fargate over managed or self-managed node groups?

Fargate removes the need to manage servers or clusters, letting you focus only on your containers and applications.

Which node group type automatically handles node updates in EKS?

A Managed node group

B Self-managed node group

C Fargate

D On-premises nodes

Managed node groups are automatically updated by AWS, unlike self-managed nodes.

Which option lets you run containers without managing EC2 instances?

A Self-managed node group

B Managed node group

C Fargate

D Auto Scaling group

Fargate runs containers serverlessly without EC2 instance management.

Who is responsible for scaling in a self-managed node group?

A You manage scaling manually

B Scaling is not possible

C Fargate scales automatically

D AWS automatically scales

In self-managed node groups, you handle scaling yourself.

Which node group type is best if you want full control over EC2 instances?

A Managed node group

B Lambda

C Fargate

D Self-managed node group

Self-managed node groups give you full control over EC2 instances.

What is a main advantage of managed node groups over self-managed?

A You must manage updates manually

B AWS handles node lifecycle management

C You cannot scale nodes

D They do not support Kubernetes

Managed node groups let AWS handle provisioning, updates, and scaling.

Explain the differences between managed node groups, self-managed node groups, and Fargate in AWS EKS.

Think about who manages the servers and how scaling and updates happen.

Describe a scenario where using Fargate would be better than using managed or self-managed node groups.

Consider ease of use and operational overhead.

Practice

1. Which type of node group in AWS EKS automatically manages the worker nodes for you?

easy

A. On-premises node group

B. Managed node group

C. Fargate

D. Self-managed node group

Solution

1. Step 1: Understand node group types in EKS

   Managed node groups are designed to let AWS handle the worker nodes, including updates and scaling.

2. Step 2: Compare with other node groups

   Self-managed node groups require manual management of EC2 instances, and Fargate runs containers without servers.

3. Final Answer:

   Managed node group -> Option B

4. Quick Check:

   Managed node group = automatic worker node management [OK]

Hint: Managed node groups mean AWS manages nodes for you [OK]

Common Mistakes:

• Confusing self-managed with managed node groups
• Thinking Fargate manages EC2 instances
• Assuming on-premises node groups are managed by AWS

2. Which of the following is the correct way to specify a Fargate profile in AWS EKS configuration?

easy

A. Specify EC2 instance types under node group

B. Set up Auto Scaling group manually

C. Define selectors with namespaces and labels for Fargate profile

D. Create a launch configuration for EC2

Solution

1. Step 1: Recall Fargate profile setup

   Fargate profiles use selectors to match pods by namespace and labels to run on Fargate.

2. Step 2: Eliminate incorrect options

   EC2 instance types, Auto Scaling groups, and launch configurations relate to EC2, not Fargate.

3. Final Answer:

   Define selectors with namespaces and labels for Fargate profile -> Option C

4. Quick Check:

   Fargate profile uses selectors = Define selectors with namespaces and labels for Fargate profile [OK]

Hint: Fargate profiles use selectors, not EC2 settings [OK]

Common Mistakes:

• Trying to specify EC2 instance types for Fargate
• Confusing Auto Scaling with Fargate profiles
• Using launch configurations for Fargate

3. Given the following EKS setup, which node group type will run the pod?

apiVersion: v1
kind: Pod
metadata:
  name: myapp
  namespace: production
spec:
  containers:
  - name: app
    image: myapp:latest

Assuming a Fargate profile exists for namespace 'production' and a managed node group is also present.

medium

A. Managed node group

B. Self-managed node group

C. No node group will run the pod

D. Fargate

Solution

1. Step 1: Check pod namespace against Fargate profile

   The pod is in 'production' namespace, which matches the Fargate profile selector.

2. Step 2: Understand pod scheduling priority

   Pods matching Fargate profiles run on Fargate instead of node groups.

3. Final Answer:

   Fargate -> Option D

4. Quick Check:

   Pod in Fargate profile namespace runs on Fargate [OK]

Hint: Pod namespace matching Fargate profile means Fargate runs it [OK]

Common Mistakes:

• Assuming managed node group runs all pods
• Ignoring Fargate profile selectors
• Thinking self-managed node group runs pods by default

4. You created a self-managed node group but your pods are stuck in Pending state. What is a likely cause?

medium

A. EC2 instances in the node group are not registered with the cluster

B. Fargate profile is missing

C. Managed node group is not enabled

D. Pod namespace does not match Fargate profile

Solution

1. Step 1: Understand self-managed node group requirements

   Self-managed nodes must register with the cluster to run pods.

2. Step 2: Identify cause of Pending pods

   If EC2 instances are not registered, pods cannot schedule and remain Pending.

3. Final Answer:

   EC2 instances in the node group are not registered with the cluster -> Option A

4. Quick Check:

   Unregistered EC2 nodes cause Pending pods [OK]

Hint: Self-managed nodes must register to run pods [OK]

Common Mistakes:

• Assuming Fargate profile affects self-managed nodes
• Thinking managed node group must be enabled for self-managed nodes
• Ignoring node registration status

5. You want to run a highly scalable application without managing any servers. Which AWS EKS node group option should you choose and why?

hard

A. Fargate, because it runs containers without managing servers

B. Managed node group, because AWS handles node updates automatically

C. Self-managed node group, because you control EC2 instances directly

D. On-premises nodes, because they offer full control

Solution

1. Step 1: Identify requirement for no server management

   The question asks for running containers without managing servers.

2. Step 2: Compare node group options

   Self-managed and managed node groups require managing or at least maintaining EC2 instances. Fargate runs containers serverless.

3. Step 3: Confirm scalability and management

   Fargate automatically scales and removes server management burden.

4. Final Answer:

   Fargate, because it runs containers without managing servers -> Option A

5. Quick Check:

   No server management means Fargate [OK]

Hint: No servers to manage? Choose Fargate [OK]

Common Mistakes:

• Choosing self-managed for no server management
• Confusing managed node groups with serverless
• Selecting on-premises nodes for cloud scalability