Skip to content

Commit 0afd555

Browse files
authored
Merge pull request #38248 from apinnick/oadp72-configuration
OADP-72: Configuration
2 parents 1ae0d4c + 1f86aa7 commit 0afd555

File tree

5 files changed

+93
-8
lines changed

5 files changed

+93
-8
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2096,8 +2096,8 @@ Topics:
20962096
# - Name: Application backup and restore
20972097
# Dir: application_backup_and_restore
20982098
# Topics:
2099-
# - Name: Application backup and restore
2100-
# File: placeholder
2099+
# - Name: Configuring OADP
2100+
# File: configuring-oadp
21012101
- Name: Control plane backup and restore
21022102
Dir: control_plane_backup_and_restore
21032103
Topics:
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
[id="configuring-oadp"]
2+
= Configuring the OpenShift API for Data Protection
3+
include::modules/common-attributes.adoc[]
4+
:context: configuring-oadp
5+
6+
toc::[]
7+
8+
You can set Velero resource allocations and enable self-signed CA certificates for the OpenShift API for Data Protection (OADP).
9+
10+
include::modules/oadp-setting-resource-limits-and-requests.adoc[leveloffset=+1]
11+
include::modules/oadp-self-signed-certificate.adoc[leveloffset=+1]

backup_and_restore/application_backup_and_restore/placeholder.adoc

Lines changed: 0 additions & 6 deletions
This file was deleted.
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * backup_and_restore/application_backup_and_restore/configuring-oadp.adoc
4+
5+
[id="oadp-self-signed-certificate_{context}"]
6+
= Enabling self-signed CA certificates
7+
8+
You must enable a self-signed CA certificate for object storage by editing the `DataProtectionApplication` custom resource (CR) manifest to prevent a `certificate signed by unknown authority` error.
9+
10+
.Prerequisites
11+
12+
* You must have the OpenShift API for Data Protection (OADP) Operator installed.
13+
14+
.Procedure
15+
16+
* Edit the `spec.backupLocations.velero.objectStorage.caCert` parameter and `spec.backupLocations.velero.config` parameters of the `DataProtectionApplication` CR manifest:
17+
+
18+
[source,yaml]
19+
----
20+
apiVersion: oadp.openshift.io/v1alpha1
21+
kind: DataProtectionApplication
22+
metadata:
23+
name: <dpa-sample>
24+
spec:
25+
...
26+
backupLocations:
27+
- name: default
28+
velero:
29+
provider: aws
30+
default: true
31+
objectStorage:
32+
bucket: <bucket>
33+
prefix: <prefix>
34+
caCert: <base64_encoded_cert_string> <1>
35+
config:
36+
insecureSkipTLSVerify: "false" <2>
37+
...
38+
----
39+
<1> Specify the Base46-encoded CA certificate string.
40+
<2> Must be `false` to disable SSL/TLS security.
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * backup_and_restore/application_backup_and_restore/configuring-oadp.adoc
4+
5+
[id="oadp-setting-resource-limits-and-requests_{context}"]
6+
= Setting Velero CPU and memory resource allocations
7+
8+
You set the CPU and memory resource allocations for the `Velero` pod by editing the `DataProtectionApplication` custom resource (CR) manifest.
9+
10+
.Prerequisites
11+
12+
* You must have the OpenShift API for Data Protection (OADP) Operator installed.
13+
14+
.Procedure
15+
16+
* Edit the values in the `spec.configuration.velero.podConfig.ResourceAllocations` block of the `DataProtectionApplication` CR manifest, as in the following example:
17+
+
18+
[source,yaml]
19+
----
20+
apiVersion: oadp.openshift.io/v1alpha1
21+
kind: DataProtectionApplication
22+
metadata:
23+
name: <dpa-sample>
24+
spec:
25+
...
26+
configuration:
27+
velero:
28+
podConfig:
29+
resourceAllocations:
30+
limits:
31+
cpu: "1" <1>
32+
memory: 512Mi <2>
33+
requests:
34+
cpu: 500m <3>
35+
memory: 256Mi <4>
36+
----
37+
<1> Specify the value in millicpus or CPU units. Default value is `500m` or `1` CPU unit.
38+
<2> Default value is `512Mi`.
39+
<3> Default value is `500m` or `1` CPU unit.
40+
<4> Default value is `256Mi`.

0 commit comments

Comments
 (0)