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

Customizing CPU and Memory should be independent of each other for Velero deployment

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Blocker Blocker
    • OADP 1.0.3
    • None
    • OADP
    • None
    • False
    • Hide

      None

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

      if a user defines memory limit, then they also have to define a CPU limit. Setting only a memory limit will set the CPU value to zero because of default int value. This should not be the case. Expected behavior should be that if the user customizes memory limit and does not specify the CPU limit then instead of assigning zero as the CPU limit, the default CPU limit value should be used.

              rhn-engineering-dymurray Dylan Murray
              spampatt@redhat.com Shubham Pampattiwar
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: