feat(vikunja): watchdog for the token the board and the factory share #573
No reviewers
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
webgrip/homelab-cluster!573
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/litellm-ingress-ploeg"
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?
One OpenBao entry (
secret/vikunja/mcpapi_token) authenticates both the MCP bridge and ploegd's tracker write-backs. When it expired on 2026-08-11 the board lost its agent and ploegd crash-looped at boot — routing-as-a-file resolves project names through this token, so an invalid one is fatal rather than cosmetic. The only trace was in pod logs nobody was tailing; it was found hours later, by hand, mid-benchmark.A daily CronJob exercises the credential the way its consumers do and fails the Job when it stops working, so the estate's existing KubeJobFailed alert is the pager — no new alerting plumbing.
Not a countdown, though three weeks' warning is what you actually want: Vikunja bars API tokens from the token-management routes, so a token cannot read its own expiry (measured —
/api/v1/tokensanswers invalid token to a valid API token). Mint with a long expiry until that changes.🤖 Generated with Claude Code
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.