--- title: Architecting Kubernetes clusters — choosing a worker... description: An in-depth architectural analysis weighs the trade-offs between deploying Kubernetes clusters with fewer large worker nodes versus many small ones. Topics... canonical: https://daily.dev/posts/architecting-kubernetes-clusters-choosing-a-worker-node-size-cbhqusj43 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Architecting Kubernetes clusters — choosing a worker node size | daily.dev og:description: An in-depth architectural analysis weighs the trade-offs between deploying Kubernetes clusters with fewer large worker nodes versus many small ones. Topics... og:url: https://daily.dev/posts/architecting-kubernetes-clusters-choosing-a-worker-node-size-cbhqusj43 og:image: https://api.daily.dev/og/posts/CBHqUSj43.png og:image:alt: Architecting Kubernetes clusters — choosing a worker node size og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Architecting Kubernetes clusters — choosing a worker node size **[LearnKube](https://daily.dev/sources/learnkube)** · 23 min read · 0 upvotes · 0 comments ## Summary An in-depth architectural analysis weighs the trade-offs between deploying Kubernetes clusters with fewer large worker nodes versus many small ones. Topics covered include reserved kubelet/OS resources and how they scale with instance size, resource utilization efficiency, resiliency and replication limits, autoscaling lead time and increments, container image pull overhead, kubelet API request rates against the control plane, node/pod count limits tied to IP addressing, and storage disk-attachment limits for StatefulSets. The piece concludes there is no universal answer, mixed node sizes are valid, and points to a companion instance calculator tool. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How much CPU and memory does the kubelet reserve on a Kubernetes worker node? Kubernetes reserves CPU in tiers: 6% of the first core, 1% of the second core, 0.5% of cores three and four, and 0.25% of any cores above four. Memory reservations are tiered too: 25% of the first 4GB, 20% of the next 4GB, 10% of the next 8GB, 6% of the next 112GB, and 2% above 128GB, plus a 100MB eviction threshold on top. _Anyone sizing worker nodes for kubernetes tracks details like these on daily.dev before provisioning capacity._ ### Why do smaller Kubernetes worker nodes waste more resources than larger ones? Smaller nodes waste proportionally more resources because kubelet and OS overhead is reserved per node rather than per cluster. A comparison of one 4 vCPU/32GB node versus seven 1 vCPU/4GB nodes running identical replicas showed the single large node reserved only 2.9GB and 80m CPU total, while the seven small nodes reserved 7.7GB and 360m CPU combined for the same workload. _Weighing node size options for a kubernetes cluster is easier with resource comparisons like this on daily.dev._ ### How many pods can I run on a single Kubernetes node? Most cloud providers allow between 110 and 250 pods per node, while the kubelet's own default maxPods setting is 110. This limit is usually driven by the cloud provider's IP addressing scheme rather than kubelet capacity, since each node typically gets a /24 subnet with 254 usable addresses shared among its pods. _Developers planning kubernetes node capacity can dig into limits like this on daily.dev._ ## Similar posts on daily.dev - [Beyond Basic Scaling: Advanced Kubernetes Resource Strategies](https://daily.dev/posts/beyond-basic-scaling-advanced-kubernetes-resource-strategies-jllrphq4i) · The New Stack · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes) [View this post on daily.dev](https://daily.dev/posts/architecting-kubernetes-clusters-choosing-a-worker-node-size-cbhqusj43) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Architecting Kubernetes clusters — choosing a worker node size","url":"https://daily.dev/posts/architecting-kubernetes-clusters-choosing-a-worker-node-size-cbhqusj43","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/architecting-kubernetes-clusters-choosing-a-worker-node-size-cbhqusj43"},"datePublished":"2026-08-31T11:20:04.596Z","dateModified":"2026-08-31T11:20:35.165Z","description":"An in-depth architectural analysis weighs the trade-offs between deploying Kubernetes clusters with fewer large worker nodes versus many small ones. Topics...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/54f65722cc8345e9f70b6e82e457f2e2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/54f65722cc8345e9f70b6e82e457f2e2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"LearnKube","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"LearnKube","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/90786df1b5d44abb91a090a0b6c81517","url":"https://daily.dev/sources/learnkube"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/architecting-kubernetes-clusters-choosing-a-worker-node-size-cbhqusj43","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes","timeRequired":"PT23M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"LearnKube","item":"https://daily.dev/sources/learnkube"},{"@type":"ListItem","position":3,"name":"Architecting Kubernetes clusters — choosing a worker node size"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/architecting-kubernetes-clusters-choosing-a-worker-node-size-cbhqusj43#faq","mainEntity":[{"@type":"Question","name":"How much CPU and memory does the kubelet reserve on a Kubernetes worker node?","acceptedAnswer":{"@type":"Answer","text":"Kubernetes reserves CPU in tiers: 6% of the first core, 1% of the second core, 0.5% of cores three and four, and 0.25% of any cores above four. Memory reservations are tiered too: 25% of the first 4GB, 20% of the next 4GB, 10% of the next 8GB, 6% of the next 112GB, and 2% above 128GB, plus a 100MB eviction threshold on top. Anyone sizing worker nodes for kubernetes tracks details like these on daily.dev before provisioning capacity."}},{"@type":"Question","name":"Why do smaller Kubernetes worker nodes waste more resources than larger ones?","acceptedAnswer":{"@type":"Answer","text":"Smaller nodes waste proportionally more resources because kubelet and OS overhead is reserved per node rather than per cluster. A comparison of one 4 vCPU/32GB node versus seven 1 vCPU/4GB nodes running identical replicas showed the single large node reserved only 2.9GB and 80m CPU total, while the seven small nodes reserved 7.7GB and 360m CPU combined for the same workload. Weighing node size options for a kubernetes cluster is easier with resource comparisons like this on daily.dev."}},{"@type":"Question","name":"How many pods can I run on a single Kubernetes node?","acceptedAnswer":{"@type":"Answer","text":"Most cloud providers allow between 110 and 250 pods per node, while the kubelet's own default maxPods setting is 110. This limit is usually driven by the cloud provider's IP addressing scheme rather than kubelet capacity, since each node typically gets a /24 subnet with 254 usable addresses shared among its pods. Developers planning kubernetes node capacity can dig into limits like this on daily.dev."}}]} ```