Four things that picked up attention this week, with what we think of each. The originals are linked; read them. This page only tells you why they matter for a small self-hosted setup.

1. An empty resources: {} quietly downgrades your pods on Kubernetes 1.34 to 1.36

Original: An Empty resources: {} Makes Kubernetes 1.34 to 1.36 Pods BestEffort on devops-daily.com (also on dev.to ).

The claim: if a pod sets spec.resources: {} at pod level, the kubelet classifies it as BestEffort even when every container has requests and limits. The authors measured it on k3s 1.34, 1.35 and 1.36: oom_score_adj jumped to 1000, and next to a busy neighbour a pod that requested half a CPU got 0.06 to 0.08 cores instead of about 0.57. A namespace quota that blocks BestEffort pods rejected it. On 1.37.1 the classes were correct. GitLab Runner's Kubernetes executor generates that empty block from version 18.10.0 to 19.4.3.

Our take: a useful correction to folklore as well.…