Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-946

openshift-apiserver must function with external OIDC

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • L
    • 1
    • 0

      Feature Overview (aka. Goal Summary)

      openshift-apiserver has dependencies on some oauth-apiserver APIs.  Those interactions need updating, while maintaining functionality.  If functionality cannot be maintained, we must know and make failures clear.

      Goals (aka. expected user outcomes)

      APIs must work.  Some known failures

      1. project request limit admission plugin will no longer function.  This limitation must be clear to customer.  Likely a failure setting the label 
      2. oc new-project fails.  this is the entry point for many openshift how-tos since pre-3.0. We need to get this working again.
      3. there may be more.  All usages of APIs served by the oauth-apiserver are suspect

      Requirements (aka. Acceptance Criteria):

      A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.

      Out of Scope

      High-level list of items that are out of scope. Initial completion during Refinement status.

      Background

      Provide any additional context is needed to frame the feature. Initial completion during Refinement status.

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.

              wcabanba@redhat.com William Caban
              deads@redhat.com David Eads
              Abu H Kashem, Vu Dinh
              Wei Sun Wei Sun
              Andrea Hoffer Andrea Hoffer
              David Eads David Eads
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: