fleetd

You've already forked fleetd

Code Issues 75 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Compare commits

base: fleet/fleetd:worker/435-fixed-policy-cap-fe11de-12

fleet/fleetd:v1.1.0 fleet/fleetd:v1.0.0

compare: fleet/fleetd:5d422f85faeeacee07be325c13d9abd6bb2f0d92

Branches Tags

fleet/fleetd:v1.1.0 fleet/fleetd:v1.0.0

1 Commits

worker/435-fixed-policy-cap-fe11de-12 .. 5d422f85fa

Author	SHA1	Message	Date
ltms	5d422f85fa	Merge #436 : make fixed placement honour maxLoad (fleetd #435 ) CI / contract (push) Successful in 48s Details CI / build (push) Successful in 1m37s Details fixed was the one automatic policy that ignored maxLoad, and it is the default for an absent placement: key. It now gates on the same shared atCap predicate weighted and round-robin use, and falls through to the next candidate rather than refusing. Verified here: 1555 tests green (main was 1548, +7 new methods), 0 compile errors. Mutation battery, control 113 green: - atCap boundary >= -> > KILLED (15 tests, across all 3 policies) - drop cap check in fixed walk KILLED (3 tests) - weightExcluded -> false KILLED (2 pre-existing tests) Neither live host is affected today: both run placement: weighted (Mac fleetd.yaml:210, fleet01 fleetd.yaml:172), and weighted already skipped at-cap candidates via PlacementPolicyUtil.available. This aligns fixed with the other policies and with maxLoad's documented contract.	2026-09-10 08:54:18 +02:00

Author

SHA1

Message

Date

ltms

5d422f85fa

Merge #436 : make fixed placement honour maxLoad (fleetd #435 )

CI / contract (push) Successful in 48s

Details

CI / build (push) Successful in 1m37s

Details

fixed was the one automatic policy that ignored maxLoad, and it is the
default for an absent placement: key. It now gates on the same shared
atCap predicate weighted and round-robin use, and falls through to the
next candidate rather than refusing.

Verified here: 1555 tests green (main was 1548, +7 new methods), 0
compile errors. Mutation battery, control 113 green:
  - atCap boundary >= -> >        KILLED (15 tests, across all 3 policies)
  - drop cap check in fixed walk  KILLED (3 tests)
  - weightExcluded -> false       KILLED (2 pre-existing tests)

Neither live host is affected today: both run placement: weighted (Mac
fleetd.yaml:210, fleet01 fleetd.yaml:172), and weighted already skipped
at-cap candidates via PlacementPolicyUtil.available. This aligns fixed
with the other policies and with maxLoad's documented contract.

2026-09-10 08:54:18 +02:00

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Expand all files Collapse all files

Compare commits

1 Commits worker/435-fixed-policy-cap-fe11de-12 .. 5d422f85fa

Diff Content Not Available

1 Commits

worker/435-fixed-policy-cap-fe11de-12 .. 5d422f85fa