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

Monitoring stack needs to function with external OIDC only

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Auth
    • False
    • Hide

      None

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

      Feature Overview (aka. Goal Summary)

      The monitoring stack needs to function when external OIDC is configured and the internal oauth-server and oauth-apiserver are removed.

      Goals (aka. expected user outcomes)

      User workflows, both UI driven and CLI/script/http-request driven should work without modification when using external OIDC.

      Based on the "remove embedded oauth-server" experiment, this isn't working as desired.  Likely due to the usage of the oauth-proxy, but we're not sure.

      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.

            rh-ee-rfloren Roger Florén
            deads@redhat.com David Eads
            Roger Florén
            Eric Paris
            Wei Sun Wei Sun
            Brian Burt Brian Burt
            David Eads David Eads
            Senthamilarasu S Senthamilarasu S
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: