Feature Overview (aka. Goal Summary)  

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

With the availability (as of 4.19) of External Secrets Operator (TP), SSCSI (GA), and cert-manager (GA). It now becomes more relevant to consider having a functional console plugin for management of secrets within OpenShift. Currently, the OpenShift console is capable of listing secrets, but the above mentioned operators provide a larger range of feature that the current console is not able to handle. A secrets management console plugin would encompass the CRDs from cert-manager, ESO, and SSCSI and allow for rotation/update of secrets and providers associated with these operators.

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.

A customer should be able to install the plugin and manage CRDs for the above mentioned operators: cert-manager, eso, and sscsi. 

This also means being able to take advantage of some, if not all, of the features associated with secret management. Such as:

• add/delete
• rotation
• revocation (where applicable)

We should also consider having a default revocation flow for secrets (to be more opinionated). This could include having a feature that pushes an event to all affected pods, kills all affected pods, or actually updates pods if possible.

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.

• provide a plugin for the openshift console
• the plugin should be able to manage resources for:

• • cert-manager crds (Issuer, Certificate, etc)
  • sscsi crds (Provider, Secrets)
  • eso crds (Provider, Secrets, Generators, etc)
• Access should be based on the users' credentials as would be expected

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>