Additional Velero configuration
If the cluster is running slowly, you may need to adjust the Velero resource limits as well as the default liveness and readiness probe parameters to ensure that backup and restore operations work properly.
The below table shows the Velero values and settings that may need to be adjusted if your cluster is running slowly.
| Parameter | Description | Default value |
|---|---|---|
| velero.nodeAgent.resources.requests.memory | Memory requests | 128Mi |
| velero.nodeAgent.resources.limits.memory | Memory limits | 512Mi |
| velero.nodeAgent.resources.requests.cpu | CPU requests | 500m |
| velero.nodeAgent.resources.limits.cpu | CPU limits | 1000m |
| velero.nodeAgent.livenessProbe.initialDelaySeconds | LivenessProbe initialDelaySeconds |
10 |
| velero.nodeAgent.livenessProbe.periodSeconds | LivenessProbe periodSeconds | 30 |
| velero.nodeAgent.livenessProbe.timeoutSeconds=10 | LivenessProbe timeoutSeconds | 5 |
| velero.nodeAgent.livenessProbe.failureThreshold | LivenessProbe failureThreshold | 5 |
| velero.nodeAgent.readinessProbe.initialDelaySeconds | ReadinessProbe initialDelaySeconds | 10 |
| velero.nodeAgent.readinessProbe.periodSeconds | ReadinessProbe periodSeconds | 30 |
| velero.nodeAgent.readinessProbe.timeoutSeconds | ReadinessProbe timeoutSeconds | 5 |
| velero.nodeAgent.readinessProbe.failureThreshold | ReadinessProbe failureThreshold | 5 |