InseeFrLab / InseeFrLab/helm-charts-databases
helm chart postgres
- Dominant language
- Mustache
- Stars
- 7
- Forks
- 17
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Description
What about adding two fields handle by bitnami:
persistentVolumeClaimRetentionPolicy:
whenDeleted: {{ .Values.primary.persistentVolumeClaimRetentionPolicy.whenDeleted }}
If Delete then he delete the pvc if Retain he kept it the user should then decide the behaviour?
and the other field:
{{- if and .Values.primary.persistence.enabled .Values.primary.persistence.existingClaim }}
- name: data
persistentVolumeClaim:
claimName: {{ tpl .Values.primary.persistence.existingClaim $ }}
if user put an existingClaim it could restart on a previous existing one.
It's not full user experence but add some behaviour
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue concerns the PostgreSQL Helm chart and the primary persistence values, including persistentVolumeClaimRetentionPolicy and existingClaim. Start by tracing those values through the chart templates and render the chart with each persistence configuration; done means both requested behaviors are represented correctly in the rendered manifests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100