---
title: "Comment by Ryan Hamonangan on \"The Myths (and Costs) of Running Node.js on Kubernetes\" | Hashnode"
description: "i have been manage node on k8s for years. from my experience. it depends based on application types. is it b2b? employees only? set auto minimum higher on worki"
url: "https://hashnode.com/posts/the-myths-and-costs-of-running-nodejs-on-kubernetes/68d162e1907f0daa5f595ce4/comment/68d2bae5ab874e92bc113bb7"
---

[Discussion](https://hashnode.com/posts/the-myths-and-costs-of-running-nodejs-on-kubernetes/68d162e1907f0daa5f595ce4)

Comment [The Myths (and Costs) of Running Node.js on Kubernetes](https://hashnode.com/posts/the-myths-and-costs-of-running-nodejs-on-kubernetes/68d162e1907f0daa5f595ce4)

[Sep 23, 2025](https://hashnode.com/posts/the-myths-and-costs-of-running-nodejs-on-kubernetes/68d162e1907f0daa5f595ce4/comment/68d2bae5ab874e92bc113bb7)

i have been manage node on k8s for years. from my experience. it depends based on application types.

is it b2b? employees only? set auto minimum higher on working hours.

is it only crud/db + some http call to another vendor? yeah burstable as this article mention

is it running some heavy duty worker. like sharp (image processing) / report server using puppeteer for example. so its nodejs but underneath it there is something like c++ Library. then autonscale based on metrics is good.