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

Document aws s3 md5sum checksum changes.

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • Sprint 13-MMSDOCS 2024
    • 1
    • Critical
    • 10
    • 3.333
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • No

      Description of problem:

      Documentation required for related bug: https://issues.redhat.com/browse/OADP-4274

      When using the velero-plugin-for-aws in AWS s3, no changes required

      When using the velero-plugin for-aws w/ S3 compat or MCG object storage providers, please note the MD5 checksum algorithm options .

       

          # The checksum algorithm to use for uploading objects to S3.
    # The Supported values are  "CRC32",  "CRC32C", "SHA1", "SHA256".
    # If the value is set as empty string "", no checksum will be calculated and attached to 
    # the request headers.
    #
    # Optional (defaults to "CRC32")
    checksumAlgorithm: "CRC32"

       

      See: https://github.com/openshift/velero-plugin-for-aws/blob/oadp-1.4/backupstoragelocation.md

      A customer must know the supported types of MD5Sum 

      A customer can set the `backupLocation.velero.config.checksumAlgoritm` to the following:

      "" = disabled

      "CRC32",

      "CRC32C",

      "SHA1",

      "SHA256".

      Example:

      spec:
  backupLocations:
  - name: default
    velero:
      config:
        checksumAlgorithm: ""

      Full MCG Example:

      apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  name: ts-dpa
  namespace: openshift-adp
spec:
  backupLocations:
  - name: default
    velero:
      config:
        checksumAlgorithm: ""
        insecureSkipTLSVerify: "true"
        profile: noobaa
        region: noobaa
        s3ForcePathStyle: "true"
        s3Url: https://s3-openshift-storage.apps.oadp-83541.qe.devcluster.openshift.com
      credential:
        key: cloud
        name: cloud-credentials
      default: true
      objectStorage:
        bucket: oadp835412rbvm
        prefix: velero
      provider: aws
  configuration:
    velero:
      defaultPlugins:
      - openshift
      - aws
      - csi

      IBM s3 providers:

      If a customer is using IBM S3 object storage the key value must be set to:

      checksumAlgorithm: ""

      S3 compatible providers may vary in their implementation and adjustments to the checksumAlgorithm may be required for OADP to operator properly.

       

      Possible error messages seen the Velero logs:

      https://docs.aws.amazon.com/AmazonS3/latest/API/API_Error.html

       

      Changes to the amazon s3 sdk

      https://aws.amazon.com/blogs/aws/new-additional-checksum-algorithms-for-amazon-s3/

       

       

       

       

       

              rhn-support-shdeshpa Shruti Deshpande
              wnstb Wes Hayutin
              Sachin Singla Sachin Singla
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: