---
title: "Discussion on \".NET Container OOMKilled in Kubernetes: Root Cause and Fix\" | Hashnode"
description: "Discussion on \".NET Container OOMKilled in Kubernetes: Root Cause and Fix\". Your .NET container is OOMKilled in Kubernetes. The real causes - GC heap limits, Server GC, DATAS - and the exact settings that fix each one."
url: "https://hashnode.com/posts/dotnet-container-oomkilled-kubernetes/6aa3ed6398fce027490119c4"
---

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

Discussion

# [.NET Container OOMKilled in Kubernetes: Root Cause and Fix](https://codingdroplets.com/dotnet-container-oomkilled-kubernetes?utm_source=hashnode&utm_medium=feed)

Your .NET container is OOMKilled in Kubernetes. The real causes - GC heap limits, Server GC, DATAS - and the exact settings that fix each one.

Sep 11 · 11 min read · codingdroplets.com  
Read the article

-   [#net](https://hashnode.com/tag/net)
-   [#aspnet-core](https://hashnode.com/tag/aspnet-core)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#docker](https://hashnode.com/tag/docker)
-   [#performance](https://hashnode.com/tag/performance)
-   [#devops](https://hashnode.com/tag/devops)
-   [#memory-management](https://hashnode.com/tag/memory-management)

## Written by

[Coding Droplets](https://hashnode.com/@codingdroplets)

@codingdroplets

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

Build, Scale & Master .NET with Clean, Practical Tutorials

## Responses

Markdown supported · ⌘↵ to post

No responses yet.