concourse / concourse/concourse-chart
specify PersistentVolume selector in postgres.persistence
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 160
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
My cluster has a staticdisk StorageClass where the volumes do not get created by a provisioner.
I normally handle this by writing PersistentVolume and PersistentVolumeClaim specs manually, where the claim has a selector that finds the volume by label, like:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: ci-data
namespace: ci
...
spec:
storageClassName: staticdisk
selector:
matchLabels:
name: "ci-data"
...
This would work with your chart too, if I could add a selector to the claim that it generates. (the volume itself would remain my problem / outside the scope of the chart)
As far as I tried its not possible right now.
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 by locating the Helm chart's postgres.persistence values and the template that generates its PersistentVolumeClaim. Check how existing persistence settings are rendered, then verify that a configured selector appears in the generated claim without requiring the chart to create the PersistentVolume.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgres
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100