--- title: Running Kubernetes Clusters on Limited Hardware | daily.dev description: A discussion on the challenges and trade-offs of running multiple Kubernetes clusters on shared, limited hardware. Key topics include Go's CPU-bound scheduler... canonical: https://daily.dev/posts/running-kubernetes-clusters-on-limited-hardware-yayf6qkvi twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Running Kubernetes Clusters on Limited Hardware | daily.dev og:description: A discussion on the challenges and trade-offs of running multiple Kubernetes clusters on shared, limited hardware. Key topics include Go's CPU-bound scheduler... og:url: https://daily.dev/posts/running-kubernetes-clusters-on-limited-hardware-yayf6qkvi og:image: https://api.daily.dev/og/posts/YAyF6qkvI.png og:image:alt: Running Kubernetes Clusters on Limited Hardware 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. # Running Kubernetes Clusters on Limited Hardware **[Ardan Labs \(YouTube\)](https://daily.dev/sources/ardanlabs-youtube)** · 1 min read · 8 upvotes · 0 comments ## Summary A discussion on the challenges and trade-offs of running multiple Kubernetes clusters on shared, limited hardware. Key topics include Go's CPU-bound scheduler behavior and how it interacts with Kubernetes CPU quotas, the risk of node saturation when consolidating many clusters and services onto the same nodes, and the intentional goal of driving up node utilization to reduce waste. The conversation highlights that most small EKS/GKE clusters are highly underutilized, and consolidation is the aim — but quality-of-service boundaries and workload-specific node requirements must be carefully managed. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why are typical small Kubernetes clusters on EKS or GKE underutilized? Small three-to-five node EKS or GKE clusters that most companies spin up tend to be highly underutilized at the node level. Consolidating multiple clusters and their services onto fewer, shared nodes is one approach to drive up utilization, though it requires careful CPU quota management and quality-of-service boundaries since Kubernetes balances scheduling based on the number of CPUs available per node. _Teams weighing cluster consolidation strategies can track practical utilization tradeoffs on daily.dev._ ### How does Go's runtime scheduler affect CPU usage in Kubernetes pods? Go's runtime includes its own scheduler that runs programs in a CPU-bound mode, spawning only as many threads as there are available cores. This interacts with Kubernetes CPU quotas, which not only schedule workloads but also try to balance how much software runs on a node based on its CPU count, making thread and quota tuning important when packing many services onto shared nodes. _Engineers tuning Go workloads under Kubernetes CPU limits can follow related scheduling insights on daily.dev._ ## Similar posts on daily.dev - [Where does a pod actually run?](https://daily.dev/posts/where-does-a-pod-actually-run--1qpnnyh2q) · Medium · 5 upvotes · 0 comments - [Kubernetes Requests and Limits: How to Right-Size Pods Without Breaking Reliability](https://daily.dev/posts/kubernetes-requests-and-limits-how-to-right-size-pods-without-breaking-reliability-2idykp32g) · Cast AI · 0 upvotes · 0 comments - [AKS Is Growing – Along With Its Kubernetes Utilization Problem](https://daily.dev/posts/aks-is-growing-along-with-its-kubernetes-utilization-problem-ydffnox87) · Cloud Native Now · 1 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#golang](https://daily.dev/tags/golang) [View this post on daily.dev](https://daily.dev/posts/running-kubernetes-clusters-on-limited-hardware-yayf6qkvi) ```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":"Running Kubernetes Clusters on Limited Hardware","url":"https://daily.dev/posts/running-kubernetes-clusters-on-limited-hardware-yayf6qkvi","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/running-kubernetes-clusters-on-limited-hardware-yayf6qkvi"},"datePublished":"2026-08-04T18:32:48.734Z","dateModified":"2026-09-13T20:07:49.381Z","description":"A discussion on the challenges and trade-offs of running multiple Kubernetes clusters on shared, limited hardware. Key topics include Go's CPU-bound scheduler...","image":"https://i.ytimg.com/vi/QJA-DbZdkTk/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/QJA-DbZdkTk/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Ardan Labs (YouTube)","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":"Ardan Labs (YouTube)","logo":"https://media.daily.dev/image/upload/s--YJq0Do2x--/f_auto,q_auto/v1780213598/logos/ardanlabs-youtube?_a=BAMAMiWQ0","url":"https://daily.dev/sources/ardanlabs-youtube"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/running-kubernetes-clusters-on-limited-hardware-yayf6qkvi","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":8},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,golang","timeRequired":"PT1M","video":{"@type":"VideoObject","name":"Running Kubernetes Clusters on Limited Hardware","description":"A discussion on the challenges and trade-offs of running multiple Kubernetes clusters on shared, limited hardware. Key topics include Go's CPU-bound scheduler...","thumbnailUrl":"https://i.ytimg.com/vi/QJA-DbZdkTk/sddefault.jpg","uploadDate":"2026-08-04T18:32:48.734Z","duration":"PT1M","url":"https://api.daily.dev/r/YAyF6qkvI","embedUrl":"https://www.youtube.com/embed/QJA-DbZdkTk"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Ardan Labs (YouTube)","item":"https://daily.dev/sources/ardanlabs-youtube"},{"@type":"ListItem","position":3,"name":"Running Kubernetes Clusters on Limited Hardware"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/running-kubernetes-clusters-on-limited-hardware-yayf6qkvi#faq","mainEntity":[{"@type":"Question","name":"Why are typical small Kubernetes clusters on EKS or GKE underutilized?","acceptedAnswer":{"@type":"Answer","text":"Small three-to-five node EKS or GKE clusters that most companies spin up tend to be highly underutilized at the node level. Consolidating multiple clusters and their services onto fewer, shared nodes is one approach to drive up utilization, though it requires careful CPU quota management and quality-of-service boundaries since Kubernetes balances scheduling based on the number of CPUs available per node. Teams weighing cluster consolidation strategies can track practical utilization tradeoffs on daily.dev."}},{"@type":"Question","name":"How does Go's runtime scheduler affect CPU usage in Kubernetes pods?","acceptedAnswer":{"@type":"Answer","text":"Go's runtime includes its own scheduler that runs programs in a CPU-bound mode, spawning only as many threads as there are available cores. This interacts with Kubernetes CPU quotas, which not only schedule workloads but also try to balance how much software runs on a node based on its CPU count, making thread and quota tuning important when packing many services onto shared nodes. Engineers tuning Go workloads under Kubernetes CPU limits can follow related scheduling insights on daily.dev."}}]} ```