potoftea

I am aware of it, are you aware that Kubernetes assigned Burstable Qos if you don't defined CPU requests and limits?

What I'm trying to say that while try to avoid one pitfall you fall right into an other - in short there are good reasons to use cpu limits.

This doens't match what I've read.

IF you don't set limit to cpu & memory, your pod QoS will be burstable and from kernel/cgroup perspective this process can be killed - it's only question of oom_score_adj.

OOMScore from linux - https://www.freedesktop.org/software/systemd/man/latest/syst...

I can't comment about about other statement.

But there are serious drawbacks if you don't set requests/limits for mission-critical process, is that they can be killed by kernel to free some resources (if the node reach max resource usage)

When you don't set cpu/memory limit your pod QoS class is burstable, which better then BestEffort, but still get assigned `oom_score_adj` score. IMHO you almost 99% you want `Guaranteed` for critical process.

1. oom_score_adj - https://kubernetes.io/docs/concepts/scheduling-eviction/node...

2. Guaranteed - https://kubernetes.io/docs/tasks/configure-pod-container/qua...

3. QoS - https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/

Does Kubegres works with any TCP proxy, and if does - is there any recommendations which one? Running ingress via Load Balancer is quite costly option in cloud context. At the moment is seems that nodeport is only realistic alternative.