Feature Overview (aka. Goal Summary)  

As a customer, I will need to update identities in my cluster, on upgrades, due to operational needs or other situations. This feature is to ensure that hypershift has the ability to:
1. change/manage identities
2. Keep track of the status of the operations

Goals (aka. expected user outcomes)

A customer can update identities in the cluster if the platform requires that changed or if the customer has a need to leverage a different identity after the cluster is created

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.

• Is this just CP MIs? Or does it also include WIs?
• AFAIK, the day 0 experience is:
• • customer passes the MIs to CS
  • CS gets the msi dataplane info
  • CS puts the data into secrets in the KV
  • CS creates the HC and plugs in the secret names
• What's this look like day 2?

re, in the feature overview: Keep track of the status of the operations

Wouldn't this be on CS just the same?Not sure this part of the feature falls on us?

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>