Skip to content

fix(gateway): use dedicated NFS mount path and remove skills emptyDir#107

Open
jacoblee-io wants to merge 1 commit intomainfrom
fix/gateway-nfs-mount-path
Open

fix(gateway): use dedicated NFS mount path and remove skills emptyDir#107
jacoblee-io wants to merge 1 commit intomainfrom
fix/gateway-nfs-mount-path

Conversation

@jacoblee-io
Copy link
Collaborator

Problem

  1. Gateway mounts the NFS PVC at /app/.siclaw/user-data — same name as agentbox's internal user-data path, causing confusion. The NFS root contains MySQL, Prometheus, Grafana data alongside siclaw data.
  2. Gateway has an unnecessary skills emptyDir volume — root filesystem is already writable, SkillFileWriter can write directly.

Solution

  • Change gateway NFS mount path to /app/.siclaw/agentbox-user-data — dedicated path that won't collide with agentbox internals
  • Remove skills emptyDir volume and mount from gateway deployments
  • Update defaults in k8s-spawner.ts, gateway-main.ts, Helm values/templates, and k8s/gateway-deployment.yaml

Test plan

  • Gateway starts and ensureUserDir() creates directories at /app/.siclaw/agentbox-user-data/users/{userId}/{wsId}
  • AgentBox pods start correctly (no change to agentbox mounts)
  • SkillFileWriter still writes skills to /app/.siclaw/skills on container filesystem

…emptyDir

- Change gateway NFS mount from /app/.siclaw/user-data to
  /app/.siclaw/agentbox-user-data to avoid collision with agentbox
  internal paths
- Remove unnecessary skills emptyDir from gateway (root filesystem
  is writable, SkillFileWriter can write directly)
- Update defaults in k8s-spawner, gateway-main, helm values/templates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant