Cluster Health: readable on Kubernetes, no pile-up after rollouts (K-A3) #258

Merged
jcoffey-dev merged 1 commits from feat/cluster-health-pods into main 2026-11-20 07:33:25 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 1c06da14d9 Cluster Health: readable on Kubernetes, no pile-up after rollouts (K-A3)
ci / build (pull_request) Skipped
ci / publish (pull_request) Skipped
ci / notices (pull_request) Successful in 56s
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m14s
On Kubernetes a node's hostname is its pod's name, and a pod's name is
never used again. Every pod a rollout replaced (and every finished Job
pod, like the chart's upgrade hook) kept a lease that went Silent and
stayed counted for a day: the lab after a few restarts showed 5 of 10
nodes up, in red, with five healthy pods running.

clusterHealth.ts reads a pod's name (Deployment <name>-<hash>-<5>, Job
<name>-<5>, Kubernetes' vowel-free alphabet). A silent lease with a pod's
name is a pod that's gone: left out of the count and listed on one line
instead of a red card. Only a Deployment with no pod renewing at all
counts as down, once. Silent servers that aren't pods count as before.

The roster groups pods under what made them (inbuxa-mta: 2 of 2 pods
up), each card titled with the pod's own part, full name on hover.
Attention and the command center use the same counts.
2026-11-20 00:30:38 -07:00