Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-3049

Re-enable FIPS compliance

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • Operator
    • None
    • Re-enable FIPS compliance
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 100% To Do, 0% In Progress, 0% Done
    • 0
    • 0

      Epic Goal

      • State the desired outcome of this epic in one sentence
      • Re-enable FIPS buy using rhel-els base images.

      Why is this important?

      • As a product that security related, we should be compliant with standards such as FIPS.

      Scenarios

      1. Baremetal usage of kata should met FIPS compliance on FIPS enabled clusters
      2. ...
      3. ...

      Acceptance Criteria 

      (The Epic is complete when...)

      1. Builds pass CVP FIPS checks
      2. ..
      3. ..

      Additional context:

      From JP Jung the PM for OCP FIPS:

      "Do not use UBI if you claim "FIPS mode" or plan to support FIPS 140. Use the rhel-els image."

      We have removed the FIPS compliant notation is 1.5.3.  To add it back we need to build

            Unassigned Unassigned
            cmeadors@redhat.com Cameron Meadors
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: