Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

There are enough general requests coming in from customers that we should consider a generic approach to "supporting" third party CA's, for the most part this involves installing the appropriate Issuer image. Most out of tree repos do this via helm or some simple Deployment. 

After the install, the CRDs for the Issuer appear to be supported.

We should consider a generic way of allowing customers to install their "preferred" custom Issuer images via a flag or other parameter. This would enable Red Hat to support any Issuer in a repeatable manner, without having the customer have to manually install Issuers. 

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.

• Provide customer with an API or parameter to supply custom Issuer images
• Enable customers to install custom or self-provided Issuer images at operator install time.
• Manage installed Issuers alongside the operator. If the operator is uninstalled, the Issuers should also be uninstalled

Non-Goals

• Not expected to validate customer provided Issuer images. 
• Not expected to support customer provided Issuers.
• Not expected to manage upgrade of issuer
  • Customers would be expected to trigger an update of the Issuer by updating the Subscription object of the Operator.

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.

• Parameter or flag that enables customer to supply custom Issuer image

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.

• https://issues.redhat.com/browse/RFE-4259
• https://issues.redhat.com/browse/RFE-7937
• https://issues.redhat.com/browse/RFE-4133
• https://issues.redhat.com/browse/RFE-6176
• https://issues.redhat.com/browse/RFE-5059
•  

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>