Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-23766

BnR Adv Config misnamed/placed (prob should be requirements)

XMLWordPrintable

    • Quality / Stability / Reliability
    • 4
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      I am not exactly sure why this was placed in "adv config" when this has one section and that is Resource limits; but then it is about Valero. We should reserve adv config for actual adv config the user has to do.

      This is more of a resource/requirements topic; there are examples in other areas of the doc for this type of info. This is usually a requirements topic or something similar. We can discuss if you want.

      Please place this accordingly the following content:

      dr4hub-advanced-configuration
      = Backup and restore advanced configuration

      You can further configure backup and restore by viewing the following sections:

      //this short description does not really match the header below and the header doesn't match the topic. It seems this is a whole topic about Velero?

      resource-requests-and-limits
      == Resource requests and limits customization

      When Velero is initially installed, Velero pod is set to the default CPU and memory limits as defined in the following sample:

      [source,yaml]


      resources:
      limits:
      cpu: "1"
      memory: 256Mi
      requests:
      cpu: 500m
      memory: 128Mi


      The limits from the previous sample work well with some scenarios, but might need to be updated when your cluster backs up a large number of resources. For instance, when back up is run on a hub cluster that manages 2000 clusters, then the Velero pod fails due to the out-of-memory error (OOM). The following configuration allows for the backup to complete for this scenario:

      [source,yaml]


      limits:
      cpu: "2"
      memory: 1Gi
      requests:
      cpu: 500m
      memory: 256Mi


      To update the limits and requests for the Velero pod resource, you need to update the `DataProtectionApplication` resource and insert the `resourceAllocation` template for the Velero pod. View the following sample:

      [source,yaml]


      apiVersion: oadp.openshift.io/v1alpha1
      kind: DataProtectionApplication
      metadata:
      name: velero
      namespace: open-cluster-management-backup
      spec:
      ...
      configuration:
      ...
      velero:
      podConfig:
      resourceAllocations:
      limits:
      cpu: "2"
      memory: 1Gi
      requests:
      cpu: 500m
      memory: 256Mi


      additional-resources-dr4hub-adv
      == Additional resources

      https://content-stage.docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.15/html-single/business_continuity/index#dr4hub-advanced-configuration

              rh-ee-ofischer Oliver Fischer
              bswope@redhat.com Brandi Swope
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: