Uploaded image for project: 'Cloud Infrastructure Security & Compliance'
  1. Cloud Infrastructure Security & Compliance
  2. CMP-3114

Implement support for Compliance Operator on ARM architecture

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • compliance-operator-1.7.0
    • None
    • None
    • None
    • co-arm-support
    • BU Product Work
    • 0
    • False
    • None
    • False
    • Not Selected
    • In Progress
    • CMP-2960 - Compliance Operator support on ARM (CIS OCP 1.7.0 and FedRAMP Moderate Revision 4)
    • CMP-2960Compliance Operator support on ARM (CIS OCP 1.7.0 and FedRAMP Moderate Revision 4)
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      Implement support and testing for running the Compliance Operator on ARM clusters.

      Why is this important?

      Several OpenShift users are using ARM, and it provides cost savings, which we could leverage in CI.

      Scenarios

      1. As a user, I want to be able to install the Compliance Operator on an ARM OpenShift cluster and leverage it to scan the environment, so that I can use the findings in audit reports
      2. As an OpenShift engineer, I want my patches to be tested on ARM clusters so that we prevent regressions on ARM architecture when releasing the Compliance Operator.

      Acceptance Criteria

      • Must have periodic weekly CI that runs some subset of profiles on ARM architecture
      • Must have gating CI jobs in the ComplianceAsCode/compliance-operator repository that tests each PR on an ARM cluster
      • Must set the appropriate ARM architecture annotations in bundle metadata.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              lbragsta@redhat.com Lance Bragstad
              lbragsta@redhat.com Lance Bragstad
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: