scheduled-backups hardcoded imediate spec

[dejanu]

The ScheduledBackup template currently does not allow overriding the immediate flag.

{{ if .Values.backups.enabled }}
{{ $context := . -}}
{{ range .Values.backups.scheduledBackups -}}
---
apiVersion: postgresql.cnpg.io/v1
kind: ScheduledBackup
metadata:
  name: {{ include "cluster.fullname" $context  }}-{{ .name }}
  namespace: {{ include "cluster.namespace" $ }}
  labels: {{ include "cluster.labels" $context | nindent 4 }}
spec:
  immediate: true
  schedule: {{ .schedule | quote }}
  method: {{ .method }}
  backupOwnerReference: {{ .backupOwnerReference }}
  cluster:
    name: {{ include "cluster.fullname" $context }}
{{ end -}}
{{ end }}

[dosubot]

Hi @dejanu! I'm Dosu and I’m helping the charts team.

The ScheduledBackup Helm template currently hardcodes immediate: true and does not allow overriding this via values.yaml or other chart values—there is no parameterization for this field in the template or values file, so it always triggers an immediate backup when the resource is created (source).

There was a previous attempt to make the immediate flag configurable via a pull request, but it was closed and not merged (source). There is also an open pull request proposing more advanced backup configuration, including support for the immediate flag, but it is not yet part of the official chart (source).

If you want to make immediate configurable right now, you can modify your local Helm template like this:

spec:
  immediate: {{ .immediate | default true }}

Then, in your values.yaml, add an immediate field for each scheduled backup:

backups:
  scheduledBackups:
    - name: my-backup
      schedule: "0 0 0 * * *"
      method: volumeSnapshot
      backupOwnerReference: cluster
      immediate: false

This will allow you to control the immediate flag per backup. If you want official support, keep an eye on the open PR for future releases.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.