uat: the harness's cluster is declared, and the health check stops racing the restart - #81
Merged
Merged
Conversation
…cing the restart The k3d lexicon (chant 0.41.15) reaches the UAT harness: uat/cluster/ is the smallest chant project that can exist — one declarable, one lexicon, dev-only — and up.sh builds the SimpleConfig from it instead of spelling flags. chant's ownership marker lands on every node's Docker labels, which is what lets a live read tell this cluster from one it does not own. m80 itself stays a single Go binary; this is harness infrastructure, and the boundary is written where the node prerequisite is introduced. Riding along: the harness image default catches up to v0.4.0 (it pointed at v0.2.0 — the drift #75 is about), the CLUSTER override refuses when it disagrees with the declared name, and the final health check polls instead of reading once — the env patches restart the operator, the connectivity line lands seconds after the rollout reports done, and a healthy stack reported itself broken by exactly that gap during this change's own proof run. Proven: just uat-up from nothing → "AWS connectivity confirmed"; labels verified on the node; just uat-down cleans up. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WVmBmk6XERjKxHa4HyezvT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The k3d lexicon adoption, m80's half — with the boundary stated plainly: m80 stays a single Go binary with no companions. What changes is the UAT harness's infrastructure: its k3d cluster was the one piece of it spelled as CLI flags.
uat/cluster/— the smallest chant project that can exist (one declarable, one lexicon,private: true, dev-only).up.shbuilds the SimpleConfig from it andk3d cluster create --configconsumes it verbatim; chant's ownership marker rides onto every node's Docker labels. node + npm join the harness prerequisites, documented where the table already lived.CLUSTERoverride refuses on disagreement with the declared name — one cluster created, a different one addressed is the failure it prevents.Proven live:
just uat-upfrom nothing →AWS connectivity confirmed: account=000000000000; ownership labels verified on the server node's Docker config;just uat-downcleans up.🤖 Generated with Claude Code
https://claude.ai/code/session_01WVmBmk6XERjKxHa4HyezvT