Skip to content

Latest commit

 

History

History
57 lines (48 loc) · 1.92 KB

resource_req_limits.md

File metadata and controls

57 lines (48 loc) · 1.92 KB

Resource Requests and Limits Customization

Setting resource limits and requests for Velero and Node Agent Pods

In order to set specific resource(cpu, memory) limits and requests for the Velero pod, you need use the configuration.velero.podConfig.resourceAllocations specification field in the oadp_v1alpha1_dpa.yaml file during the deployment.

For instance, the configuration.velero.podConfig.resourceAllocations can look somewhat similar to:

  configuration:
    velero:
      podConfig:
        resourceAllocations:
          limits:
            cpu: "2"
            memory: 512Mi
          requests:
            cpu: 500m
            memory: 256Mi

Similarly, you can use the configuration.nodeAgent.podConfig.resourceAllocations specification field for setting specific resource limits and requests for the Node Agent pods.

  configuration:
    nodeAgent:
    [...]
      podConfig:
        resourceAllocations:
          limits:
            cpu: "2"
            memory: 512Mi
          requests:
            cpu: 500m
            memory: 256Mi

Note:

  • The values for the resource requests and limits flags follow the same format as Kubernetes resource requirements

  • Also, if the configuration.velero.podConfig.resourceAllocations / configuration.nodeAgent.podConfig.resourceAllocations is not defined by the user, then the default resources specification for Velero/Node Agent pod(s) is:

    resources:
  requests:
    cpu: 500m
    memory: 128Mi

This differs from upstream Velero/Node Agent pod(s) in that the default resources which has resource limits as well as resource requests.