Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-648

Remove default limits for velero and restic pods

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Normal
    • OADP 1.1.0
    • OADP 1.1.0, OADP 1.0.3
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • No
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

    Description

      Description of problem:

      We currently define default limits for the velero and restic pods which we should instead leave empty to prevent a user from failing backups/restores due to these limits and they can always adjust as necessary.

      Version-Release number of selected component (if applicable):

      1.1.0

      How reproducible:

      100%

      Steps to Reproduce:
      1. Install OADP
      2. Create DPA without setting limits/requests

      Actual results:

      Observe default limits on velero deployment or restic daemonset:

      resources:
        limits:
          cpu: "1"
          memory: 256Mi

      Expected results:

      No default limits exist on velero or restic deployment/daemonset

      Additional info:

      Check that velero and restic pods no longer contain resource limits.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. OADP-590 OpenShift ADP Backup is stuck in progress

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OADP-595 Backing up with restic gets stucked without progress due to OOMKilled on restic pods

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/oadp-operator#773: OADP-648 Don't set default pod resource limits

          GitHub openshift/openshift-docs#47769: OADP-311 Node selector usage for velero and restic

          GitHub openshift/openshift-docs#48202: WIP: OADP-399: Add resource requests/limits to Troubleshooting

          Activity

            People

              tkaovila@redhat.com Tiger Kaovilai
              rhn-engineering-dymurray Dylan Murray
              Maya Peretz Maya Peretz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: