Myasnikov Daniil 64253ed2db docs(platform): narrow two claims to what actually holds ...

The bold lead asked for the limit to stay above the largest
memory request "declared in any system namespace", which is
wider than the check beneath it and wider than the truth. A
container declaring its own memory limit is never defaulted, so
its request cannot collide with the knob. The script already
filters those out; the lead now says the same thing.

The VPA sentence stated proportional limit rescaling as a
general property. It holds only under controlledValues:
RequestsAndLimits. That is the upstream default and no VPA in
packages/ sets the field at all, so the claim is true here, but
under RequestsOnly a raised request would leave the defaulted
limit behind and produce exactly the admission rejection the
paragraph rules out. Say which case is being relied on.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>

2026-08-19 16:25:23 +05:00

..

backup-classes.md

docs(backups): note to-copy MongoDB restore needs target creds that can read the source bucket

2026-08-12 12:00:33 +04:00

resource-presets.md

docs(operations): resource presets reference

2026-05-11 21:10:19 +03:00

seaweedfs-431-rename-recovery.md

fix(seaweedfs): read the chart name first-match, fail the fake on unmodelled calls

2026-07-27 13:52:59 +05:00

system-memory-limits.md

docs(platform): narrow two claims to what actually holds

2026-08-19 16:25:23 +05:00