ModelEngine-Group / ModelEngine-Group/nexent
fix(k8s): correct shared storage PV rendering
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.9k
- Forks
- 731
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 172
Description
Problem
The local PersistentVolume rendered for nexent-skills-pv places accessModes under capacity, causing Kubernetes quantity validation to reject the manifest.
Expected behavior
All shared-storage PersistentVolumes render schema-valid Kubernetes resources with accessModes under spec.
Acceptance
- Local-mode shared storage renders valid PV and PVC YAML.
- Tests cover workspace, skills, logs, and memory-plugin storage resources.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the rendering code for nexent-skills-pv and the other shared-storage PV/PVC resources, then inspect how local-mode manifests place accessModes. Run the existing storage-related tests, or add focused coverage for workspace, skills, logs, and memory-plugin resources; done means all local-mode PV and PVC YAML is schema-valid with accessModes under spec.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100