Chapter 14. EtcdBackup [operator.openshift.io/v1alpha1]


Description

# EtcdBackup provides configuration options and status for a one-time backup attempt of the etcd 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

14.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.

14.1.1. .spec

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

pvcName

string

pvcName specifies the name of the PersistentVolumeClaim (PVC) which binds a PersistentVolume where the etcd backup file 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.

14.1.2. .status

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

backupJob

object

backupJob is the reference to the Job that executes the backup. Optional

conditions

array

conditions provide details on the status of the etcd backup job.

conditions[]

object

Condition contains details for one aspect of the current state of this API Resource.

14.1.3. .status.backupJob

Description
backupJob is the reference to the Job that executes the backup. Optional
Type
object
Required
  • name
  • namespace
Expand
PropertyTypeDescription

name

string

name is the name of the Job. Required

namespace

string

namespace is the namespace of the Job. this is always expected to be "openshift-etcd" since the user provided PVC is also required to be in "openshift-etcd" Required

14.1.4. .status.conditions

Description
conditions provide details on the status of the etcd backup job.
Type
array

14.1.5. .status.conditions[]

Description
Condition contains details for one aspect of the current state of this API Resource.
Type
object
Required
  • lastTransitionTime
  • message
  • reason
  • status
  • type
Expand
PropertyTypeDescription

lastTransitionTime

string

lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable.

message

string

message is a human readable message indicating details about the transition. This may be an empty string.

observedGeneration

integer

observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.

reason

string

reason contains a programmatic identifier indicating the reason for the condition’s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.

status

string

status of the condition, one of True, False, Unknown.

type

string

type of condition in CamelCase or in foo.example.com/CamelCase.

14.2. API endpoints

The following API endpoints are available:

  • /apis/operator.openshift.io/v1alpha1/etcdbackups

    • DELETE: delete collection of EtcdBackup
    • GET: list objects of kind EtcdBackup
    • POST: create an EtcdBackup
  • /apis/operator.openshift.io/v1alpha1/etcdbackups/{name}

    • DELETE: delete an EtcdBackup
    • GET: read the specified EtcdBackup
    • PATCH: partially update the specified EtcdBackup
    • PUT: replace the specified EtcdBackup
  • /apis/operator.openshift.io/v1alpha1/etcdbackups/{name}/status

    • GET: read status of the specified EtcdBackup
    • PATCH: partially update status of the specified EtcdBackup
    • PUT: replace status of the specified EtcdBackup
HTTP method
DELETE
Description
delete collection of EtcdBackup
Expand
Table 14.1. HTTP responses
HTTP codeReponse body

200 - OK

Status schema

401 - Unauthorized

Empty

HTTP method
GET
Description
list objects of kind EtcdBackup
Expand
Table 14.2. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackupList schema

401 - Unauthorized

Empty

HTTP method
POST
Description
create an EtcdBackup
Expand
Table 14.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 14.4. Body parameters
ParameterTypeDescription

body

EtcdBackup schema

 
Expand
Table 14.5. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackup schema

201 - Created

EtcdBackup schema

202 - Accepted

EtcdBackup schema

401 - Unauthorized

Empty

Expand
Table 14.6. Global path parameters
ParameterTypeDescription

name

string

name of the EtcdBackup

HTTP method
DELETE
Description
delete an EtcdBackup
Expand
Table 14.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 14.8. HTTP responses
HTTP codeReponse body

200 - OK

Status schema

202 - Accepted

Status schema

401 - Unauthorized

Empty

HTTP method
GET
Description
read the specified EtcdBackup
Expand
Table 14.9. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackup schema

401 - Unauthorized

Empty

HTTP method
PATCH
Description
partially update the specified EtcdBackup
Expand
Table 14.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 14.11. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackup schema

401 - Unauthorized

Empty

HTTP method
PUT
Description
replace the specified EtcdBackup
Expand
Table 14.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 14.13. Body parameters
ParameterTypeDescription

body

EtcdBackup schema

 
Expand
Table 14.14. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackup schema

201 - Created

EtcdBackup schema

401 - Unauthorized

Empty

Expand
Table 14.15. Global path parameters
ParameterTypeDescription

name

string

name of the EtcdBackup

HTTP method
GET
Description
read status of the specified EtcdBackup
Expand
Table 14.16. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackup schema

401 - Unauthorized

Empty

HTTP method
PATCH
Description
partially update status of the specified EtcdBackup
Expand
Table 14.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 14.18. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackup schema

401 - Unauthorized

Empty

HTTP method
PUT
Description
replace status of the specified EtcdBackup
Expand
Table 14.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 14.20. Body parameters
ParameterTypeDescription

body

EtcdBackup schema

 
Expand
Table 14.21. HTTP responses
HTTP codeReponse body

200 - OK

EtcdBackup schema

201 - Created

EtcdBackup 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