Rongsong Shen
19104d315b
Validation-only, no code changes. Confirmed the complete spec end-to-end against a freshly built controller+scheduler+apiserver: default 9-resource set + one deliberately-unregistered name -> VERDICT resources=10 rejected=1 result=FAIL (exit 1), attributable specifically to the rejected name, not a false PASS; positive control (defaults only) -> VERDICT resources=9 rejected=0 result=PASS (exit 0). All 27 individual layer-checks (9 resources x 3 layers) MATCH; raw scheduler.log/apiserver.log trace lines independently verified against tasks 4.1/4.2's documented format; rejection confirmed non-silent across 4 independent log sources; cleanup and log preservation confirmed. Surfaced (but correctly did not fix, out of boundary) bug-1583: the apiserver stores resource-location updates with zero name validation, even for names the controller/scheduler both reject. Confirmed this does not affect this feature's own correctness - accept/reject is determined entirely by cmd_resupdate()'s controller-side follow-up query, before any layer is checked. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||