Spotlight

Three Weeks in the Trenches: Hunting a 4GB Native Memory Leak That .NET Couldn’t See

Kalyan Josyula

This case study shows how a team traced repeated pod OOM kills in ASP.NET Core to native memory growth from zombie SignalR connections, glibc fragmentation, and kernel socket buffers.

More articles →

Tools and utilities

  • k10s

    k10s is a terminal dashboard for watching multiple Kubernetes clusters at once, with side-by-side views, health signals, warnings, and recent logs in one screen.

  • KubeDiagrams

    KubeDiagrams is a tool that automatically generates visual architecture diagrams from Kubernetes manifests, Helm charts, and live clusters.

  • H8s (Homernetes)

    H8s is a home infrastructure project combining Kubernetes with Talos OS security, running on 2 N100 mini PCs with GitOps deployment via ArgoCD.

  • Nelm: Helm replacement

    Nelm is meant to be a direct replacement for Helm 3, providing first-class Helm chart support yet improving on what Helm 3 offers.

  • Valkey cluster operator

    Valkey Operator is a Kubernetes operator that automates deployment and lifecycle management of Valkey clusters and instances with features like automated installation and configuration management.

More projects →

Events starting soon

Discover more events onn Kube Events →

The Namespaces Scaling Trap
The Namespaces Scaling Trap

Most teams scale Kubernetes by thinking about pods and nodes. At Render, Brian Stack ran into a different dimension: hundreds of thousands of namespaces per cluster, multiplied across DaemonSets that list-watch every namespace.

Brian explains how Render traced the issue through Calico and Vector, worked with upstream maintainers, and turned memory profiling into operational wins: lower node costs, lighter API-server load, and faster rollouts.

In this interview:

  • Why namespaces can become a hidden scaling bottleneck
  • How DaemonSets multiply memory and control-plane pressure
  • How profiling, staging clusters, and upstream collaboration freed 7 TiB
  • Why pushing from an 80% fix to a complete fix can make teams faster

Learn from production

More case studies →

Matching jobs

    • Data Engineer with Brillio

    • Salary: $64.8K to $2.48L a year

    • Location: based in the office in Bangalore, KA, IN

    • Tech stack: Kubernetes, AWS, Docker, Scala, Shell, SQL, DynamoDB, Spark, Cloudformation

    • DevOps Engineer with 3Pillar

    • Salary: $126.9K to $302.5K a year

    • Location: remote from

    • Tech stack: Kubernetes, AWS, Azure, GCP, Docker, C++, Java, Redis, Cloudformation, Terraform

    • DevOps Engineer with Aircall

    • Salary: $99.9K to $275K a year

    • Location: based in the office in Paris, FR

    • Tech stack: Kubernetes, AWS, Docker, Go, Python, Typescript, Cloudformation, Terraform, Datadog

    • DevOps Engineer with Aledade

    • Salary: $49.5K to $539K a year

    • Location: remote from

    • Tech stack: Kubernetes, AWS, Docker, Go, Python, Pulumi, Terraform, GitHub Actions

    • DevOps Engineer with Apply Digital

    • Salary: $67.5K to $539K a year

    • Location: remote from

    • Tech stack: Kubernetes, GCP, Docker, Python, Shell, Terraform, GitHub Actions, Gitlab

Discover more Kubernetes jobs on Kube Careers →

Subscribe to Learn Kubernetes Weekly

Trusted by 77K engineers. Delivered 183 issues and counting.

or subscribe via

Build something

More tutorials →

Call for Papers closing soon

  1. 1

    days

    code.talks

    The Call For Paper is open until 15 May 2026 at GMT-4. More info →
    • Location: Hamburg, DE

    • In-person conference organized by code.talks.

    • The conference starts on the 5 November 2026.

    • Apply here
  2. 2

    days

    Devopsdays Denver

    The Call For Paper is open until 16 May 2026 at GMT-4. More info →
    • Location: Denver, CO, USA

    • In-person conference organized by Devopsdays.

    • The conference starts on the 22 September 2026.

    • Apply here
  3. 2

    days

    Michigan Technology Conference 2026

    The Call For Paper is open until 16 May 2026 at GMT-4. More info →
    • Location: Rochester, MI, USA

    • In-person conference organized by The Michigan Technology Conference Association.

    • The conference starts on the 30 October 2026.

    • Apply here
  4. 3

    days

    TechEx North America

    The Call For Paper is open until 17 May 2026 at GMT-4. More info →
    • Location: San Jose, CA, USA

    • In-person conference organized by TechEx Events.

    • The conference starts on the 19 May 2026.

    • Apply here
  5. 4

    days

    Devopsdays London

    The Call For Paper is open until 17 May 2026 at GMT-4. More info →
    • Location: London, UK

    • In-person conference organized by Devopsdays.

    • The conference starts on the 17 September 2026.

    • Apply here
  6. 4

    days

    Devopsdays Rio de Janeiro

    The Call For Paper is open until 17 May 2026 at GMT-4. More info →
    • Location: Rio de Janeiro, BR

    • In-person conference organized by Devopsdays.

    • The conference starts on the 15 August 2026.

    • Apply here
  7. 5

    days

    Kubernetes Community Days Lima 2026

    The Call For Paper is open until 19 May 2026 at GMT-4. More info →
    • Location: Lima, PE

    • In-person conference organized by KCD Lima, Perú.

    • The conference starts on the 18 July 2026.

    • Apply here

Thanks to our sponsors who make Kube Today possible

Find out more about being a sponsor →

More articles

Even more articles →