postgresql.backup.cronjob.timeZone from values.yaml is ignored
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Dears,
I try to run the postgresql backups cronjob at a specific time and another cronjob some time later. Hence, I want to avoid confusion on timezones and be explicit in both cases.
I learnt from https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml#L1300 that the bitnami postgresql helm chart supports such value.
Can we please forward all the postgresql.backup.cronjob to the respective sub helm chart?
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 bitnami/postgresql/values.yaml around the referenced backup.cronjob settings and trace how the Nextcloud chart passes PostgreSQL backup values to its subchart. Verify which cronjob fields are currently forwarded and ensure the timezone setting reaches the subchart; confirm the resulting configuration preserves the requested schedule timezone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100