Uploaded image for project: 'OpenShift Authentication'
  1. OpenShift Authentication
  2. AUTH-412

PSa enforcement deliverables in 4.14

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Critical
    • openshift-4.14
    • None
    • None
    • PSa enforcement deliverables in 4.14
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-746 - PSa enforcement deliverables in 4.14
    • OCPSTRAT-746PSa enforcement deliverables in 4.14
    • 100
    • 100% 100%
    • Hide

      We are delivering PSa enforcement mode in the near future. In this release we will make tools (such as oc debug tools for psaviolations information) available to help assess violations still seen on the cluster and prevent future violations for happening for e.g. in the kubesystem and default namespaces. 

      Show
      We are delivering PSa enforcement mode in the near future. In this release we will make tools (such as oc debug tools for psaviolations information) available to help assess violations still seen on the cluster and prevent future violations for happening for e.g. in the kubesystem and default namespaces. 

    Description

      Epic Goal*

      Deliver tools and code that helps toward PSa enforcement   

      Why is this important? (mandatory)

      What are the benefits to the customer or Red Hat?   Does it improve security, performance, supportability, etc?  Why is work a priority?

       
      Scenarios (mandatory) 

      Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

      1.  

       
      Dependencies (internal and external) (mandatory)

      What items must be delivered by other teams/groups to enable delivery of this epic. 

      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Acceptance Criteria (optional)

      Provide some (testable) examples of how we will know if we have achieved the epic goal.  

      Drawbacks or Risk (optional)

      Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

      Attachments

        Activity

          People

            slaznick@redhat.com Stanislav Laznicka
            atelang@redhat.com Anjali Telang
            Krzysztof Ostrowski, Sergiusz Urbaniak (Inactive), Stanislav Laznicka
            Krzysztof Ostrowski Krzysztof Ostrowski
            Giriyamma Karagere Ramaswamy Giriyamma Karagere Ramaswamy (Inactive)
            Andrea Hoffer Andrea Hoffer
            David Eads David Eads
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: