mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
57 lines
2.1 KiB
Plaintext
57 lines
2.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * backup_and_restore/application_backup_and_restore/configuring-oadp.adoc
|
|
// * backup_and_restore/application_backup_and_restore/oadp-aws-sts/oadp-aws-sts.adoc
|
|
// * backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc
|
|
// * backup_and_restore/application_backup_and_restore/installing/installing-oadp-azure.adoc
|
|
// * backup_and_restore/application_backup_and_restore/installing/installing-oadp-gcp.adoc
|
|
// * backup_and_restore/application_backup_and_restore/installing/installing-oadp-mcg.adoc
|
|
// * backup_and_restore/application_backup_and_restore/installing/installing-oadp-ocs.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="oadp-setting-resource-limits-and-requests_{context}"]
|
|
= Setting Velero CPU and memory resource allocations
|
|
|
|
[role="_abstract"]
|
|
You set the CPU and memory resource allocations for the `Velero` pod by editing the `DataProtectionApplication` custom resource (CR) manifest.
|
|
|
|
.Prerequisites
|
|
|
|
* You must have the OpenShift API for Data Protection (OADP) Operator installed.
|
|
|
|
.Procedure
|
|
|
|
* Edit the values in the `spec.configuration.velero.podConfig.ResourceAllocations` block of the `DataProtectionApplication` CR manifest, as in the following example:
|
|
+
|
|
[source,yaml]
|
|
----
|
|
apiVersion: oadp.openshift.io/v1alpha1
|
|
kind: DataProtectionApplication
|
|
metadata:
|
|
name: <dpa_sample>
|
|
spec:
|
|
# ...
|
|
configuration:
|
|
velero:
|
|
podConfig:
|
|
nodeSelector: <node_selector>
|
|
resourceAllocations:
|
|
limits:
|
|
cpu: "1"
|
|
memory: 1024Mi
|
|
requests:
|
|
cpu: 200m
|
|
memory: 256Mi
|
|
----
|
|
+
|
|
where:
|
|
+
|
|
`nodeSelector`:: Specifies the node selector to be supplied to Velero podSpec.
|
|
`resourceAllocations`:: Specifies the resource allocations listed for average usage.
|
|
+
|
|
[NOTE]
|
|
====
|
|
Kopia is an option in OADP 1.3 and later releases. You can use Kopia for file system backups, and Kopia is your only option for Data Mover cases with the built-in Data Mover.
|
|
|
|
Kopia is more resource intensive than Restic, and you might need to adjust the CPU and memory requirements accordingly.
|
|
==== |