mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-01-13 19:36:22 +00:00
71e0204f6a
Automatic merge from submit-queue (batch tested with PRs 45809, 46515, 46484, 46516, 45614) kubelet was sending negative allocatable values **What this PR does / why we need it**: if you set reservations > node capacity, the node sent negative values for allocatable values on create. setting negative values on update is rejected. **Which issue this PR fixes** xref https://bugzilla.redhat.com/show_bug.cgi?id=1455420 **Special notes for your reviewer**: at this time, the node is allowed to set status on create. without this change, a node was being registered with negative allocatable values. i think we need to revisit letting node set status on create, and i will send a separate pr to debate the merits of that point. ```release-note Prevent kubelet from setting allocatable < 0 for a resource upon initial creation. ```