openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 15:46:57 +01:00
Code Issues Releases Activity

Correctly adds resource requests/limits to Troubleshooting

Browse Source
This commit is contained in:
Shikha Jhala
2023-05-22 12:20:58 -04:00
committed by openshift-cherrypick-robot
parent 9c4dec2998
commit fa9f0acfc7
1 changed files with 23 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
backup_and_restore/application_backup_and_restore/troubleshooting.adoc
View File

@@ -26,6 +26,29 @@ include::modules/velero-obtaining-by-accessing-binary.adoc[leveloffset=+1]
include::modules/oadp-debugging-oc-cli.adoc[leveloffset=+1]
include::modules/migration-debugging-velero-resources.adoc[leveloffset=+1]
[id="oadp-pod-crash-resource-request"]
== Pods crash or restart due to lack of memory or CPU
If a Velero or Restic pod crashes due to a lack of memory or CPU, you can set specific resource requests for either of those resources.
include::modules/oadp-pod-crash-set-resource-request-velero.adoc[leveloffset=+2]
include::modules/oadp-pod-crash-set-resource-request-restic.adoc[leveloffset=+2]
[IMPORTANT]
====
The values for the resource request fields must follow the same format as Kubernetes resource requirements.
Also, if you do not specify `configuration.velero.podConfig.resourceAllocations` or `configuration.restic.podConfig.resourceAllocations`, the default `resources` specification for a Velero pod or a Restic pod is as follows:
[source,yaml]
----
requests:
cpu: 500m
memory: 128Mi
----
====
[id="issues-with-velero-and-admission-workbooks"]
== Issues with Velero and admission webhooks