Difference between EKS managed node group and self-managed node group

0

Hi guys! I read these two documents about EKS managed node group and self-managed node group, but I still can't understand the difference between these two types. Could you please help me explain with the simple way to understand. Thanks! https://docs.aws.amazon.com/eks/latest/userguide/worker.html https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html

Steven
asked a year ago13408 views
3 Answers
2

Let's use the Container ship analogy to answer your question. Some basics out of the way first . . .

Node = Host, or to use the analogy The Container Ship. It is where your tasks or groups of containers run.

The question here is how much control do you want over ship building?

Self Managed

With self managed, you build and maintain the ship. You specify your EC2 instance and AMI image (i.e Bottlerocket, Firecracker, Windows) You have more to do when patching your nodes and have complete control of the instance.

Managed Node

AWS manages the servers for you - You just specify the instance type, but not the AMI. Patching can be managed for you.

Fargate

The last type of node group is Fargate - This is like giving your container to someone else to ship. You don't have a ship. Your container runs on a node with other customers and you are only billed for the compute you use, not the whole node or empty ship. This is considered serverless since you don't provision or maintain servers with this node group type.

You can mix and match Node Groups on the same cluster if you desire.

profile pictureAWS
answered a year ago
profile pictureAWS
EXPERT
reviewed a year ago
  • thanks for your answer

0
Accepted Answer

With a self-managed node there is a lot you are responsible for configuring. That includes installing the kubelet, container runtime, connecting to the cluster, autoscaling, networking, and more. Most EKS clusters do not need the level of customization that self-managed nodes provide.

Managed node groups handle the lifecycle of each worker node for you. A managed node group will come with all the prerequisite software and permissions, connect itself to the cluster, and provide an easier experience for lifecycle actions like autoscaling and updates. In most cases managed node groups will reduce the operational overhead of self managing nodes and provide a much easier experience.

AWS
Noah_L
answered a year ago
profile picture
EXPERT
reviewed 8 months ago
  • thanks for your answer

  • is there any pricing difference in managed and self-managed? Let's say we will run 2 two worker nodes only, so any difference in the pricing? Also Savings plan can also be used if we opt any managed or self-managed?

  • Managed nodes only bill for the other AWS resources consumed (EC2, EBS, etc). The managed worker nodes will appear in your account and savings plans will apply to both managed and self managed nodes.

  • This AWS Document say's in self managed we do not have to manage kubelet and other things https://docs.aws.amazon.com/eks/latest/userguide/worker.html, I am more confused now

    Amazon EKS provides specialized Amazon Machine Images (AMIs) that are called Amazon EKS optimized AMIs. The AMIs are configured to work with Amazon EKS. Their components include containerd, kubelet, and the AWS IAM Authenticator. The AMIs also contain a specialized bootstrap script that allows it to discover and connect to your cluster's control plane automatically.

0

But you still need manually update the eks managed node group AMI:(

profile picture
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions