Uploaded image for project: 'Observability UI'
  1. Observability UI
  2. OU-485

Make Perses operator FIPS compliant

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • COO 1.1.0 RC
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • OBSDA-390 - Integration of Perses: backend & frontend / Internal Customers - OCP web console & RHACM console
    • NEW
    • Sprint 266

      Background

      Every component installed with COO must be compliant with FIPS, this includes the Perses operator

      Outcomes

      • The Perses operator that is installed with OCP via COO is FIPS compliant

      Steps

              Unassigned Unassigned
              gbernal@redhat.com Gabriel Bernal
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: