Specify `selector` for persistent volume claims
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
My team often has several development instances of RStudio Workbench deployed at any time. We'd like to be able to leverage creating the homeStorage persistent volume claim, but with NFS persistent volumes it's sometimes tricky to make sure that the claim binds to the correct volume. We leverage the selector feature of persistent volume to make sure the bind happens correctly.
For example, we define the spec for the PVC like so:
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 1Mi
selector:
matchLabels:
app.kubernetes.io/instance: my-workbench-deployment
pv-role: home
and it then binds to a persistent volume matching those labels.
It would be helpful if we could define a selector block when creating a persistent volume claim, which would go here:
Here's the Kubernetes documentation for it: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#selector
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
Start with charts/rstudio-workbench/templates/pvc.yaml at the referenced PVC spec. Read the surrounding template and determine how chart configuration is passed into it. Done means users can provide a Kubernetes selector for the homeStorage claim and the rendered PVC includes the requested selector fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100