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

Add FIPS Mode flag to the OADP Operator listing in OperatorHub

    XMLWordPrintable

Details

    • False
    • Hide

      None

      Show
      None
    • False
    • oadp-operator-bundle-container-1.3.1-35
    • ToDo
    • No
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

    Description

      Now that OADP is FIPS-validated, we need to update the operator listing to advertise it in OpenShift clusters. Here's the ACM operator as an example:

      Under Infrastructure features on the left

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. OADP-3355 [DOC] Release Notes for OADP 1.3.1

          • 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#1318: OADP-3495: mark FIPS compliant flag to true in operator

          GitHub openshift/oadp-operator#1319: [oadp-1.3] OADP-3495: mark FIPS compliant flag to true in operator

          Web Link RHSA-2024:126995 OpenShift API for Data Protection (OADP) 1.3.1 security and bug fix update

          Activity

            People

              wnstb Wes Hayutin
              akrohg@redhat.com Andy Krohg
              Sachin Singla Sachin Singla
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: