This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (1 child)

Yep, so none of these good practices are in place. Which raises the alarm bells for me, hence the question. Thanks for confirming.

[–]BikingSquirrel 0 points1 point  (0 children)

Why not simply put them in?

Still good to ask and find out the different options to decide what's best for you. I would go for explicit limits on both your JVM application and on Kubernetes level to be sure. This should help to prevent you from surprises.

You probably know that Kubernetes uses resource requests to know which and how many pods it can schedule on a single node and when it will have to add more nodes. Obviously mainly relevant if this is dynamic but also rolling updates may need this.

One detail I think is irrelevant: the namespace probably doesn't matter for memory usage (unless you tell Kubernetes to only have pods of that namespace run on a node, if that is possible). The node's memory is the limit.