Epic Goal*

What is our purpose in implementing this?  What new capability will be available to customers?

Identify and replace dependencies to github.com/distribution with github.com/containers in the openshift organization on Github.

 
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?

In recent v3 release, upstream distribution (github.com/distribution/distribution) has made their registry/client package internal (distribution/distribution/internal/client).

openshift/library-go's own registryclient package (openshift/library-go/pkg/image/registryclient) depends on distribution/registry/client to function.

Since we (Red Hat) are the main driving force of github.com/containers, we want to prioritize using it over github.com/distribution whenever possible.

This has recently raised in priority due to a dependency issue when solving a CVE in openshift/library-go. See openshift/library-go#1789 for details.

 
Scenarios (mandatory) 

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

1. As a Software Engineer working at Red Hat, I want to eat our own dog food so that I help improve Red Hat driven projects

 
Dependencies (internal and external) (mandatory)

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

Part of the work in this epic is to identify this.

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.  

Most (if not all) of repositories in github.com/openshift should not depend on github.com/distribution

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”