---
title: "Discussion on \"When the cluster looked idle but nothing would schedule\" | Hashnode"
description: "Discussion on \"When the cluster looked idle but nothing would schedule\". The first thing I checked was the obvious one: CPU. Our non-prod EKS workers are Karpenter-managed, and application pods had been sitting in Pending long enough that Istio and app syncs were backing u"
url: "https://hashnode.com/posts/when-the-cluster-looked-idle-but-nothing-would-schedule/6ac1c9fbe8a623698126213b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [When the cluster looked idle but nothing would schedule](https://mriduliti.hashnode.dev/when-the-cluster-looked-idle-but-nothing-would-schedule?utm_source=hashnode&utm_medium=feed)

The first thing I checked was the obvious one: CPU. Our non-prod EKS workers are Karpenter-managed, and application pods had been sitting in Pending long enough that Istio and app syncs were backing u

Oct 4 · 6 min read · mriduliti.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#eks](https://hashnode.com/tag/eks)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#karpenter](https://hashnode.com/tag/karpenter)

## Written by

[MRIDUL TIWARI](https://hashnode.com/@MridulTi)

@MridulTi

  
[View profile](https://hashnode.com/@MridulTi)

Learning in public

DevOps Engineer | Delivering Scalable, Reliable Systems | Background in Full-Stack Development (React, Next.js, Node.js, Flask, Django)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
