Skip to content

docs: a troubleshooting page, and what nixlab's version numbers mean - #64

Merged
thatbagu merged 1 commit into
mainfrom
docs/troubleshooting
Nov 21, 2026
Merged

thatbagu merged 1 commit into
mainfrom
docs/troubleshooting

Conversation

@thatbagu

Copy link
Copy Markdown
Owner
  • Troubleshooting (new page): symptom → what to run, built from what actually went wrong on a live cluster. It covers:

    • a node that won't unlock, install, or wake
    • failed nightly upgrades
    • Argo CD and Longhorn states
    • leftover pods
    • backups that fail, are locked, or need restoring
    • secrets: a missing passphrase, rotation, a lost key.

    Each row points at the tool (unlock, reinstall, wake, nixlab-restore, rekey, …), not manual steps.

  • Updates → nixlab's own versions: what patch, minor and major mean for you; every release's notes end with "Upgrading". It also says plainly that the weekly update keeps your pinned nixlab tag, so moving to a new release is your call.

The rekey row assumes #62.

🤖 Generated with Claude Code

- troubleshooting.md: what went wrong on a real cluster and the tool for
  each (a node that won't unlock or install, alerts, Argo CD and Longhorn
  states, backups that fail or need restoring, secrets).
- updates.md: patch/minor/major and what each asks of you; every release's
  notes end with Upgrading; the weekly update keeps your nixlab tag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@thatbagu
thatbagu merged commit 1eb14c1 into main Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant