Repository navigation
epic: production deployment improvements (air-gapped support, China network guidance, multi-host topology) #2218
Description
Problem Statement
- Nemoclaw currently lacks a clear path for fully air‑gapped production deployment, so users must build their own DevOps wrappers and scripts to run it safely in restricted environments.
- K3s‑based clusters and China network conditions (blocked domains) are not well documented or supported, making reliable deployment in Mainland China difficult.
- In multi‑host setups, the Openshell gateway, OpenClaw gateway, and Nemoclaw CLI can live on different namespaces, so networking is easy to misconfigure.
Proposed Design
Expected Result
Provide an official, well-documented production deployment path, including options for air-gapped or restricted environments, clear guidance for K3s and China networks, and a recommended multi-host topology with automated checks for required ports and connectivity.
Alternatives Considered
No response
Category
enhancement: feature
Checklist
- I searched existing issues and this is not a duplicate
- This is a design proposal, not a "please build this" request
Activity
wscurran commentedon Apr 22, 2026
✨ Thanks for submitting this issue that identifies a problem with production deployment — this may involve issues with air-gapped environments, K3s-based clusters, and multi-host setups.
cecilyc-july commentedon Apr 23, 2026
Since these features are of particular interest to our customers in China, I’d like to ask what you think about them. Will these features be added, and is there any roadmap you can share?
[-]production deployment improvements (air-gapped support, China network guidance, multi-host topology)[/-][+]epic: production deployment improvements (air-gapped support, China network guidance, multi-host topology)[/+]wscurran commentedon Jun 5, 2026
Hi @cecilyc-july, thanks again for raising this.
We reviewed this issue with the engineering lead and split the original request into three more focused sub-issues so each workstream can be designed, scoped, and tracked independently:
feat(install): support portable air-gapped production deployment bundles #4872 —
feat(install): support portable air-gapped production deployment bundlesdocs(networking): add K3s and Mainland China deployment guidance #4873 —
docs(networking): add K3s and Mainland China deployment guidancefeat(networking): add multi-host topology connectivity checks #4874 —
feat(networking): add multi-host topology connectivity checksCould you please take a look at those three sub-issues and let us know whether they capture the deployment problems you had in mind? If anything important is missing, especially for China customer deployments or air-gapped production workflows, we can adjust the child issues before implementation planning continues.
fix(platform): tighten 6 claims flagged by deep codebase audit
cjagwani commentedon Sep 4, 2026
Thanks for outlining these important deployment needs. We are closing this issue because the work is now tracked in #4872, #4873, and #4874.