Author on-box k3s root-cause probe parsers (C1 battery) #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Author the manual-first parsers for the on-box k3s root-cause probe battery used to debug the flapping-502 on
kai-server(o2r channel9KP5, conceptC1-onbox-rootcause).The runbook's
manual_first_gaterequires a hand-authored parser per command-id beforescripts/step.pywill run it (fail-closed: un-parsed = un-anonymized). These four command-ids had no parser, so STEP halted on them.Parsers added
All
normalize.text(lines + rc),ip_scrubbackstop, registered inparsers/_registry.yml:k3s-service—systemctl status k3s(restart/since story)k3s-journal—journalctl -u k3s --since '-30min'(apiserver/etcd/oom/panic grep surface)host-pressure—bash -lc "free -h ; df -h / /var/lib/rancher ; uptime"(OOM / etcd-disk hypotheses)recent-reboots—last -x reboot shutdown(reboot-loop hypothesis)The existing
kubectl-readyzparser is reused for the on-box readyz probe.Scope / caveat
This issue covers the parser yaml only (the gate that lets STEP run). The
public/tier thesetextprobes emit still carries timestamps + opaque ids and is not commit-safe until the anonymize stage is hardened — tracked separately in #3. Probeoutputs/are kept local-only.