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

oc (CLI) needs to be functional or fail gracefully without oauth server


    • False
    • Hide


    • False
    • XCMSTRAT-365ROSA must support external OIDC token issuers
    • 0% To Do, 0% In Progress, 100% Done
    • 1
    • 0
    • 0
    • Program Call

      Feature Overview (aka. Goal Summary)

      oc, the openshift CLI, needs as close to feature parity as we can get without the built-in oauth server and its associated user and group management.  This will enable scripts, documentation, blog posts, and knowledge base articles to function across all form factors and the same form factor with different configurations.

      Goals (aka. expected user outcomes)

      CLI users and scripts should be usable in a consistent way regardless of the token issuer configuration.

      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.


      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.

            gausingh@redhat.com Gaurav Singh
            deads@redhat.com David Eads
            Arda Guclu
            Wei Sun Wei Sun
            Andrea Hoffer Andrea Hoffer
            David Eads David Eads
            0 Vote for this issue
            12 Start watching this issue