Chapter 4. Backup [config.openshift.io/v1alpha1]


Description

Backup provides configuration for performing backups of the openshift cluster.

Compatibility level 4: No compatibility is provided, the API can change at any point for any reason. These capabilities should not be used by applications needing long term support.

Type
object
Required
  • spec

4.1. Specification

Expand
PropertyTypeDescription

apiVersion

string

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

string

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

metadata

ObjectMeta

Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

spec

object

spec holds user settable values for configuration

status

object

status holds observed values from the cluster. They may not be overridden.

4.1.1. .spec

Description
spec holds user settable values for configuration
Type
object
Required
  • etcd
Expand
PropertyTypeDescription

etcd

object

etcd specifies the configuration for periodic backups of the etcd cluster

4.1.2. .spec.etcd

Description
etcd specifies the configuration for periodic backups of the etcd cluster
Type
object
Expand
PropertyTypeDescription

pvcName

string

pvcName specifies the name of the PersistentVolumeClaim (PVC) which binds a PersistentVolume where the etcd backup files would be saved The PVC itself must always be created in the "openshift-etcd" namespace If the PVC is left unspecified "" then the platform will choose a reasonable default location to save the backup. In the future this would be backups saved across the control-plane master nodes.

retentionPolicy

object

retentionPolicy defines the retention policy for retaining and deleting existing backups.

schedule

string

schedule defines the recurring backup schedule in Cron format every 2 hours: 0 */2 * * * every day at 3am: 0 3 * * * Empty string means no opinion and the platform is left to choose a reasonable default which is subject to change without notice. The current default is "no backups", but will change in the future.

timeZone

string

The time zone name for the given schedule, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. If not specified, this will default to the time zone of the kube-controller-manager process. See https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones

4.1.3. .spec.etcd.retentionPolicy

Description
retentionPolicy defines the retention policy for retaining and deleting existing backups.
Type
object
Required
  • retentionType
Expand
PropertyTypeDescription

retentionNumber

object

retentionNumber configures the retention policy based on the number of backups

retentionSize

object

retentionSize configures the retention policy based on the size of backups

retentionType

string

retentionType sets the type of retention policy. Currently, the only valid policies are retention by number of backups (RetentionNumber), by the size of backups (RetentionSize). More policies or types may be added in the future. Empty string means no opinion and the platform is left to choose a reasonable default which is subject to change without notice. The current default is RetentionNumber with 15 backups kept.

4.1.4. .spec.etcd.retentionPolicy.retentionNumber

Description
retentionNumber configures the retention policy based on the number of backups
Type
object
Required
  • maxNumberOfBackups
Expand
PropertyTypeDescription

maxNumberOfBackups

integer

maxNumberOfBackups defines the maximum number of backups to retain. If the existing number of backups saved is equal to MaxNumberOfBackups then the oldest backup will be removed before a new backup is initiated.

4.1.5. .spec.etcd.retentionPolicy.retentionSize

Description
retentionSize configures the retention policy based on the size of backups
Type
object
Required
  • maxSizeOfBackupsGb
Expand
PropertyTypeDescription

maxSizeOfBackupsGb

integer

maxSizeOfBackupsGb defines the total size in GB of backups to retain. If the current total size backups exceeds MaxSizeOfBackupsGb then the oldest backup will be removed before a new backup is initiated.

4.1.6. .status

Description
status holds observed values from the cluster. They may not be overridden.
Type
object

4.2. API endpoints

The following API endpoints are available:

  • /apis/config.openshift.io/v1alpha1/backups

    • DELETE: delete collection of Backup
    • GET: list objects of kind Backup
    • POST: create a Backup
  • /apis/config.openshift.io/v1alpha1/backups/{name}

    • DELETE: delete a Backup
    • GET: read the specified Backup
    • PATCH: partially update the specified Backup
    • PUT: replace the specified Backup
  • /apis/config.openshift.io/v1alpha1/backups/{name}/status

    • GET: read status of the specified Backup
    • PATCH: partially update status of the specified Backup
    • PUT: replace status of the specified Backup

4.2.1. /apis/config.openshift.io/v1alpha1/backups

HTTP method
DELETE
Description
delete collection of Backup
Expand
Table 4.1. HTTP responses
HTTP codeReponse body

200 - OK

Status schema

401 - Unauthorized

Empty

HTTP method
GET
Description
list objects of kind Backup
Expand
Table 4.2. HTTP responses
HTTP codeReponse body

200 - OK

BackupList schema

401 - Unauthorized

Empty

HTTP method
POST
Description
create a Backup
Expand
Table 4.3. Query parameters
ParameterTypeDescription

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Expand
Table 4.4. Body parameters
ParameterTypeDescription

body

Backup schema

 
Expand
Table 4.5. HTTP responses
HTTP codeReponse body

200 - OK

Backup schema

201 - Created

Backup schema

202 - Accepted

Backup schema

401 - Unauthorized

Empty

Expand
Table 4.6. Global path parameters
ParameterTypeDescription

name

string

name of the Backup

HTTP method
DELETE
Description
delete a Backup
Expand
Table 4.7. Query parameters
ParameterTypeDescription

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

Expand
Table 4.8. HTTP responses
HTTP codeReponse body

200 - OK

Status schema

202 - Accepted

Status schema

401 - Unauthorized

Empty

HTTP method
GET
Description
read the specified Backup
Expand
Table 4.9. HTTP responses
HTTP codeReponse body

200 - OK

Backup schema

401 - Unauthorized

Empty

HTTP method
PATCH
Description
partially update the specified Backup
Expand
Table 4.10. Query parameters
ParameterTypeDescription

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Expand
Table 4.11. HTTP responses
HTTP codeReponse body

200 - OK

Backup schema

401 - Unauthorized

Empty

HTTP method
PUT
Description
replace the specified Backup
Expand
Table 4.12. Query parameters
ParameterTypeDescription

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Expand
Table 4.13. Body parameters
ParameterTypeDescription

body

Backup schema

 
Expand
Table 4.14. HTTP responses
HTTP codeReponse body

200 - OK

Backup schema

201 - Created

Backup schema

401 - Unauthorized

Empty

Expand
Table 4.15. Global path parameters
ParameterTypeDescription

name

string

name of the Backup

HTTP method
GET
Description
read status of the specified Backup
Expand
Table 4.16. HTTP responses
HTTP codeReponse body

200 - OK

Backup schema

401 - Unauthorized

Empty

HTTP method
PATCH
Description
partially update status of the specified Backup
Expand
Table 4.17. Query parameters
ParameterTypeDescription

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Expand
Table 4.18. HTTP responses
HTTP codeReponse body

200 - OK

Backup schema

401 - Unauthorized

Empty

HTTP method
PUT
Description
replace status of the specified Backup
Expand
Table 4.19. Query parameters
ParameterTypeDescription

dryRun

string

When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

fieldValidation

string

fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Expand
Table 4.20. Body parameters
ParameterTypeDescription

body

Backup schema

 
Expand
Table 4.21. HTTP responses
HTTP codeReponse body

200 - OK

Backup schema

201 - Created

Backup schema

401 - Unauthorized

Empty

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top