keel: move to 0.4.0, and pin the api at one replica #20

Merged

PerishFire merged 1 commit from keel-040 into main

2026-07-21 08:31:26 +00:00

PerishFire commented

2026-07-21 08:13:17 +00:00

Owner

No description provided.

PerishFire added 1 commit

2026-07-21 08:13:17 +00:00

keel: move to 0.4.0, and pin the api at one replica

guard / guard (pull_request) Failing after 5m39s

Details

c91d4005b6

Dependency line only. 0.4.0 renames set_tie to tune and reshuffles
query's internals; ensign calls none of them, checked across the tree.

The cache fix does reach ensign. It already exposes the switch — keel.toml
[cache] kind = "none" becomes Hold::None becomes core.bare() — and before
keel #105 that call left grant rows cached, so setting cache = none to
prepare a multi-replica deploy still held authority per process. It now
clears both caches.

values.yaml says why api.replicas stays at 1, at the line an operator
would raise: keel caches grants per engine instance, so a second api pod
keeps honouring a grant this one revoked until it writes. Raising it
needs the cache off first. helm lint clean.

This lands before the I8 cluster gate on purpose — replicas is exactly
the knob that arc hands over.

PerishFire force-pushed keel-040 from c91d4005b6

guard / guard (pull_request) Failing after 5m39s

Details

to c4bb21ed5d

guard / guard (pull_request) Successful in 4m6s

Details

2026-07-21 08:27:13 +00:00

Compare

PerishFire merged commit 84f0fb7ee1 into main

2026-07-21 08:31:26 +00:00

PerishFire referenced this pull request from a commit

2026-07-21 08:31:27 +00:00