Skip to content

docs: add Kubernetes namespace recovery steps #6080

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
WilliamK112 wants to merge 1 commit into from
Closed

docs: add Kubernetes namespace recovery steps #6080

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/reference/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -410,6 +410,19 @@ sudo ufw allow from "$SUBNET" to any port 8080 proto tcp
$$nemoclaw onboard
```

### Onboard fails with "Kubernetes namespace not ready"

This error usually means a previous install or onboard attempt left the local OpenShell/Kubernetes state partially initialized.
Clean up the failed setup state, then run the installer again:

```bash
$$nemoclaw uninstall --yes
curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
```

The `$$nemoclaw uninstall` command runs the version-pinned `uninstall.sh` that shipped with the installed CLI and preserves user data such as rebuild backups, workspace backups, and the sandbox registry unless you pass `--destroy-user-data`.
If the CLI is missing or broken, use the hosted `uninstall.sh` fallback from [Uninstall](../manage-sandboxes/lifecycle#uninstall), then rerun the installer.

### `connect` exits because the gateway is down

`$$nemoclaw <name> connect` checks the OpenShell gateway before it tries dashboard forwarding, SSH, or inference repair.
Expand Down
Loading