docs: add Kubernetes namespace recovery steps

[WilliamK112]

Summary- add a troubleshooting entry for the "Kubernetes namespace not ready" onboard failure- document the cleanup-first recovery path before re-running the installer- point users to the existing uninstall guidance and preserve the user-data warningFixes #6027## Validation- git diff --check- rg -n "Kubernetes namespace not ready|$$nemoclaw uninstall --yes|hosted uninstall.sh fallback|lifecycle#uninstall|www.nvidia.com/nemoclaw.sh" docs/reference/troubleshooting.mdx## Notes- npm run docs:check-agent-variants still fails on existing unrelated generated-doc drift: docs/reference/commands-nemohermes.mdx is out of sync. Run npm run docs:sync-agent-variants.

Summary by CodeRabbit

Summary by CodeRabbit* Documentation

• Added a new troubleshooting guide for onboarding failures caused by a Kubernetes namespace not being ready.
• Included a recovery flow to uninstall and reinstall after a partially failed setup.
• Clarified what the uninstall command preserves by default and how to proceed if the local uninstall step is missing or broken.

Signed-off-by: WilliamK112 164879897+WilliamK112@users.noreply.github.com

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9d12e479-a7db-4300-bd86-4e14033737e2

📥 Commits

Reviewing files that changed from the base of the PR and between df04386 and 0de7bfb.

📒 Files selected for processing (1)

• docs/reference/troubleshooting.mdx

✅ Files skipped from review due to trivial changes (1)

• docs/reference/troubleshooting.mdx

---

📝 Walkthrough

Walkthrough

Added a new troubleshooting subsection for "Kubernetes namespace not ready" onboarding failures, with cleanup and reinstall steps, default data preservation details, and a fallback path when the local uninstall script is unavailable.

Changes

Troubleshooting Documentation

Layer / File(s)	Summary
Kubernetes namespace not ready entry docs/reference/troubleshooting.mdx	Adds a troubleshooting subsection for onboarding failures caused by leftover partial Kubernetes/OpenShell state, including uninstall/reinstall recovery and fallback instructions when the local uninstall script is missing or broken.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: ericksoa

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the PR’s main doc update: adding Kubernetes namespace recovery steps.
Linked Issues check	✅ Passed	The new troubleshooting section documents the missing uninstall-and-reinstall recovery path for the Kubernetes namespace not ready failure.
Out of Scope Changes check	✅ Passed	The change stays within the documented troubleshooting fix and does not introduce unrelated scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[wscurran]

✨ Thanks for the fix. Adding the Kubernetes namespace recovery steps to troubleshooting will help users recover from this onboarding failure.

---

Related open issues:

• #6027 [All Platforms][Docs] Kubernetes namespace not ready workaround missing from troubleshooting documentation

[miyoungc]

Please resolve the DCO check failure in this PR, all of your open PRs, and future PRs.

[WilliamK112]

Closing this as superseded by #6213, which merged into main and closed #6027. I rebased locally to double-check the current state before closing: origin/main already has a Kubernetes namespace not ready troubleshooting section with the uninstall/reinstall recovery path, so keeping this PR open would now duplicate docs content.

I also added the requested PR-body DCO sign-off here before closing, and checked the other open NemoClaw PRs I have (#5674 and #5676); both already contain PR-body sign-off lines.