Error: × K8s namespace not ready ╰─▶ timed out waiting for namespace 'openshell' to exist: Error from server (NotFound): namespaces "openshell" not found
- Dominant language
- TypeScript
- Stars
- 22.5k
- Forks
- 3.1k
- Avg merge
- 1d 43m
- Merged PRs (30d)
- 718
Description
### Description
Starting OpenShell gateway pod...
Gateway start returned before healthy:
Deploying local gateway nemoclaw...
Checking Docker
Downloading gateway
Initializing environment
x Gateway failed: nemoclaw
Gateway failed to start
The gateway encountered an unexpected error during startup.
To fix:
1. Check container logs for details
openshell doctor logs --name nemoclaw
2. Run diagnostics
openshell doctor check --name nemoclaw
3. Try destroying and recreating the gateway
openshell gateway destroy --name nemoclaw && openshell gateway start
4. If the issue persists, report it at https://github.com/nvidia/openshell/issues
Error: × K8s namespace not ready
╰─▶ timed out waiting for namespace 'openshell' to exist: Error from server
(NotFound): namespaces "openshell" not found
A big reason this project is being ignored is that the installation and deployment are a nightmare. Even with a VPN, it constantly throws errors. I honestly don't see the point of Why H’s (Boss Huang's) work here—it's just a pile of steep learning curves that are over-engineered and frustrating to use. To top it off, there’s no detailed Q&A to help
### Reproduction Steps
nemoclaw onboard
### Environment
ubuntu24.04
### Debug Output
```shell
```
### Logs
```shell
```
### Checklist
- [x] I confirmed this bug is reproducible
- [x] I searched existing issues and this is not a duplicate
Contributor guide
Research direction
Start by reproducing `nemoclaw onboard` on Ubuntu 24.04, then run `openshell doctor logs --name nemoclaw` and `openshell doctor check --name nemoclaw` to inspect the gateway startup and namespace readiness failure. Done means the `openshell` namespace is found and the local gateway starts successfully; the payload names no source file or test to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100