Vouch request: harche #469
harche
started this conversation in
Vouch Request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What do you want to work on?
I want to add support for running OpenShell on existing Kubernetes clusters instead of only k3s-in-Docker. Specifically, I got NemoClaw working on OpenShift 4.21 using the agent-sandbox CRD (https://github.com/kubernetes-sigs/agent-sandbox) as the sandbox runtime. The agent-sandbox repo already has an openclaw-sandbox example, so the pieces fit together.
The main change would be giving OpenShell the option to target an existing cluster rather than always spinning up k3s inside Docker.. There's no existing issue for this yet, I plan to file one with the full design.
Some outputs from my experiments,
harpatil@harpatil-mac cri-o % curl -sk https://nemoclaw-gateway-nemoclaw-sandbox.apps.harpatil4215f.gcp.devcluster.openshift.com/ -o /dev/null -w 'HTTP %{http_code}\n' HTTP 200Why this change?
I work with OpenShift clusters and wanted to run OpenShell sandboxes on one. The current architecture bundles k3s inside Docker, which doesn't work on OpenShift, SCCs reject hardcoded UIDs, CRI-O replaces Docker, and the bootstrap assumptions don't hold.
I got it working by using the agent-sandbox CRD (kubernetes-sigs/agent-sandbox) as the sandbox runtime instead of k3s. Had to solve a few things along the way, arbitrary UID support, gateway binding, entrypoint permissions etc.
OpenShift is common in enterprise environments. Supporting existing clusters (not just embedded k3s) would make OpenShell useful to more people.
Checklist
Beta Was this translation helpful? Give feedback.
All reactions