Kubernetes memory requests don't do what you think (until you enable MemoryQoS)
Kubernetes memory management relies on cgroups to allocate resources effectively. By default, memory requests are only utilized by the scheduler, which can lead to processes being reclaimed even if they stay within their declared limits. The MemoryQoS feature, still in alpha, allows for better memory guarantees but requires specific kernel versions and configurations to function properly.
- ▪Kubernetes uses cgroups for resource management, particularly focusing on cgroups v2 for memory management.
- ▪In the default configuration, memory requests are only used by the scheduler and not passed to the kernel as memory.min.
- ▪The MemoryQoS feature allows kubelet to map memory requests to memory.min, ensuring a minimum memory allocation for processes.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Roszigit |
| Canonical URL | https://roszigit.com/en/blog/kubernetes-memory-request-limit |
| Publication time | Sun, 17 May 2026 19:53:16 +0000 |
| Retrieval time | 2026-05-17T20:03:21.009Z |
| Last seen | 2026-05-17T20:03:21.009Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | tynZddCfWjSx |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
(function(e,t,n,s,o){e[s]=e[s]||[],e[s].push({"gtm.start":(new Date).getTime(),event:"gtm.js"});var a=t.getElementsByTagName(n)[0],i=t.createElement(n),r=s!="dataLayer"?"&l="+s:"";i.async=!0,i.src="https://www.googletagmanager.com/gtm.js?id="+o+r,a.parentNode.insertBefore(i,a)})(window,document,"script","dataLayer","GTM-PM8VLKVT")<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-PM8VLKVT" height=0 width=0 style=display:none;visibility:hidden></iframe>HomeBlogKubernetes Management: Memory Request and Limit in Practice April 19, 2026 | 7 min ReadKubernetes Management: Memory Request and Limit in PracticeThis is the second part of an article series about resource management in Kubernetes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Roszigit.
Discussion
0 commentsMore from Roszigit
