---
title: "Discussion on \"Why Kubernetes In-Place Memory Resize Gets Stuck \"In Progress\" on JVM Pods\" | Hashnode"
description: "Discussion on \"Why Kubernetes In-Place Memory Resize Gets Stuck \"In Progress\" on JVM Pods\". You lowered a JVM pod's memory with an in-place resize, and the pod now shows PodResizeInProgress, an Error reason, and an old memory limit that never changes. The kubelet is not broken. It refuses to"
url: "https://hashnode.com/posts/kubernetes-pod-resize-stuck-in-progress-jvm/6af0c696398465e528bff9ff"
---

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

Discussion

[BaoKhang](https://hashnode.com/@baokhang)

17h ago

# [Why Kubernetes In-Place Memory Resize Gets Stuck "In Progress" on JVM Pods](https://baokhang.hashnode.dev/kubernetes-pod-resize-stuck-in-progress-jvm?utm_source=hashnode&utm_medium=feed)

You lowered a JVM pod's memory with an in-place resize, and the pod now shows PodResizeInProgress, an Error reason, and an old memory limit that never changes. The kubelet is not broken. It refuses to

baokhang.hashnode.dev 10 min read

[#kubernetes](https://hashnode.com/tag/kubernetes) [#java](https://hashnode.com/tag/java) [#jvm](https://hashnode.com/tag/jvm) [#kubectl](https://hashnode.com/tag/kubectl) [#devops](https://hashnode.com/tag/devops)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.