Skip to content

Commit f4a76a9

Browse files
committed
docs: Explain node_groups and worker_groups difference
1 parent e8a060f commit f4a76a9

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/faq.md

+8
Original file line numberDiff line numberDiff line change
@@ -189,3 +189,11 @@ Kubelet restricts the allowed list of labels in the `kubernetes.io` namespace th
189189
Older configurations used labels like `kubernetes.io/lifecycle=spot` and this is no longer allowed. Use `node.kubernetes.io/lifecycle=spot` instead.
190190

191191
Reference the `--node-labels` argument for your version of Kubenetes for the allowed prefixes. [Documentation for 1.16](https://v1-16.docs.kubernetes.io/docs/reference/command-line-tools-reference/kubelet/)
192+
193+
## What is the difference between `node_groups` and `worker_groups`?
194+
195+
`node_groups` are [AWS-managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html) (configures "Node Groups" that you can find on the EKS dashboard). This system is supposed to ease some of the lifecycle around upgrading nodes. Although they do not do this automatically and you still need to manually trigger the updates.
196+
197+
`worker_groups` are [self-managed nodes](https://docs.aws.amazon.com/eks/latest/userguide/worker.html) (provisions a typical "Autoscaling group" on EC2). It gives you full control over nodes in the cluster like using custom AMI for the nodes. As AWS says, "with worker groups the customer controls the data plane & AWS controls the control plane".
198+
199+
Both can be used together in the same cluster.

0 commit comments

Comments
 (0)