Skip to content

Commit 163008d

Browse files
authored
Merge pull request #48202 from RichardHoch/resource_req
OADP-399: Add resource requests/limits to Troubleshooting
2 parents 0b3f0de + 9071cbd commit 163008d

File tree

2 files changed

+58
-0
lines changed

2 files changed

+58
-0
lines changed
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * backup_and_restore/application_backup_and_restore/troubleshooting.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="oadp-pod-crash-resource-request-retics_{context}"]
7+
= Setting resource requests for a Restic pod
8+
9+
You can use the `configuration.restic.podConfig.resourceAllocations` specification field to set specific resource requests for a `Restic` pod.
10+
11+
.Procedure
12+
13+
* Set the `cpu` and `memory` resource requests in the YAML file:
14+
+
15+
.Example Restic file
16+
17+
[source,yaml]
18+
----
19+
apiVersion: oadp.openshift.io/v1alpha1
20+
kind: DataProtectionApplication
21+
...
22+
configuration:
23+
restic:
24+
podConfig:
25+
resourceAllocations:
26+
requests:
27+
cpu: 500m
28+
memory: 256Mi
29+
----
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * backup_and_restore/application_backup_and_restore/troubleshooting.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="oadp-pod-crash-resource-request-velero_{context}"]
7+
= Setting resource requests for a Velero pod
8+
9+
You can use the `configuration.velero.podConfig.resourceAllocations` specification field in the `oadp_v1alpha1_dpa.yaml` file to set specific resource requests for a `Velero` pod.
10+
11+
.Procedure
12+
13+
* Set the `cpu` and `memory` resource requests in the YAML file:
14+
+
15+
.Example Velero file
16+
17+
[source,yaml]
18+
----
19+
apiVersion: oadp.openshift.io/v1alpha1
20+
kind: DataProtectionApplication
21+
...
22+
configuration:
23+
velero:
24+
podConfig:
25+
resourceAllocations:
26+
requests:
27+
cpu: 500m
28+
memory: 256Mi
29+
----

0 commit comments

Comments
 (0)