ScheduledBackup is the Schema for the scheduledbackups API
5 top-level fields, 2 required · last changed in CloudNativePG v1.23.3
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Specification of the desired behavior of the ScheduledBackup. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
Indicates which ownerReference should be put inside the created backup resources.<br /> - none: no owner reference for created backup objects (same behavior as before the field was introduced)<br /> - self: sets the Scheduled backup object as owner of the backup<br /> - cluster: set the cluster as owner of the backup<br />
The cluster to backup
Name of the referent.
If the first backup has to be immediately start after creation or not
The backup method to be used, possible options are `barmanObjectStore`, `volumeSnapshot` or `plugin`. Defaults to: `barmanObjectStore`.
Whether the default type of backup with volume snapshots is online/hot (`true`, default) or offline/cold (`false`) Overrides the default setting specified in the cluster field '.spec.backup.volumeSnapshot.online'
Configuration parameters to control the online/hot backup with volume snapshots Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza
Control whether the I/O workload for the backup initial checkpoint will be limited, according to the `checkpoint_completion_target` setting on the PostgreSQL server. If set to true, an immediate checkpoint will be used, meaning PostgreSQL will complete the checkpoint as soon as possible. `false` by default.
If false, the function will return immediately after the backup is completed, without waiting for WAL to be archived. This behavior is only useful with backup software that independently monitors WAL archiving. Otherwise, WAL required to make the backup consistent might be missing and make the backup useless. By default, or when this parameter is true, pg_backup_stop will wait for WAL to be archived when archiving is enabled. On a standby, this means that it will wait only when archive_mode = always. If write activity on the primary is low, it may be useful to run pg_switch_wal on the primary in order to trigger an immediate segment switch.
Configuration parameters passed to the plugin managing this backup
Name is the name of the plugin managing this backup
Parameters are the configuration parameters passed to the backup plugin for this backup
The schedule does not follow the same format used in Kubernetes CronJobs as it includes an additional seconds specifier, see https://pkg.go.dev/github.com/robfig/cron#hdr-CRON_Expression_Format
If this backup is suspended or not
The policy to decide which instance should perform this backup. If empty, it defaults to `cluster.spec.backup.target`. Available options are empty string, `primary` and `prefer-standby`. `primary` to have backups run always on primary instances, `prefer-standby` to have backups run preferably on the most updated standby, if available.
Most recently observed status of the ScheduledBackup. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
The latest time the schedule
Information when was the last time that backup was successfully scheduled.
Next time we will run a backup
Source: postgresql.cnpg.io_scheduledbackups.yaml
Changes to ScheduledBackup (postgresql.cnpg.io/v1) in each CloudNativePG version, compared to the version before it.
1 property has changed the description
Released · View ScheduledBackup in v1.23.3
1 property has been added
Released · View ScheduledBackup in v1.23.0
12 properties have changed the description
Released · View ScheduledBackup in v1.22.2
12 properties have changed the description
Released · View ScheduledBackup in v1.22.0
12 properties have changed the description
Released · View ScheduledBackup in v1.21.4
2 properties have been added
Released · View ScheduledBackup in v1.21.1
1 property has been added
Released · View ScheduledBackup in v1.21.0
3 properties are now required
Released · View ScheduledBackup in v1.20.3
3 properties are no longer required
1 property has changed the description
Released · View ScheduledBackup in v1.20.0
3 properties are now required
Released · View ScheduledBackup in v1.19.5
1 property has been added
Released · View ScheduledBackup in v1.19.1
1 property has changed the description
Released · View ScheduledBackup in v1.17.2
1 property has changed the description
Released · View ScheduledBackup in v1.17.0
1 property has changed the description
Released · View ScheduledBackup in v1.16.4
1 property has been added
Released · View ScheduledBackup in v1.15.1
ScheduledBackup was first seen on this version of CloudNativePG
Released · View ScheduledBackup in v1.15.0
No examples of ScheduledBackup yet. Contribute one on GitHub.
kubespec.dev