Feature Overview (aka. Goal Summary)  

Overview

As part of ARO-HCP, we need to support asynchronous requests for creating, deleting and updating external auth IDPs in Clusters Service.

To support this feature, we need to add new status condition(s) to the HostedCluster resource. These conditions should allow the Clusters Service to see the health of the external authentication IDP configuration supplied by the user, indicating whether its been successfully applied, is ready to be used or if there were errors during creation, update or deletion.

This request, follows on from OCPSTRAT-2172. At the time, it was agreed upon that a new condition that indicates the existence of day-2 client secret(s) is to be added initially, which only check for their existence.

This issue should cover the rest of the status condition(s) required to accurately reflect the status of an external authentication IDP as well as validating the contents of the day-2 client secret(s). This status should also include validation errors (currently when configuration is invalid, the oidc configuration is not applied to the authentication resource).

The status must be available in the HostedCluster. Since there are multiple configurations in the HostedCluster, the status for each configured external auth provider should be easily identifiable by CS so it can accurately report the status back to the user.

See Phase 4: Comprehensive Status Reporting in the DDR for XCMSTRAT-574

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

<your text here>

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.

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

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

<your text here>

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.

<your text here>

Out of Scope

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

<your text here>

Background

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

<your text here>

Customer Considerations

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

<your text here>

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.

<your text here>

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.

<your text here>