Feature Overview (aka. Goal Summary)  

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

SSCSI has a feature for automatic rotation of secrets IF the upstream secrets manager updates the secret (for certain types of providers)

There is no real story for cert-manager or external secrets operator associate with automatic rotation of secrets OR revocation of secrets. 

Develop an extension to the API for cert-manager, eso, and (possibly enhance) sscsi that will detect upstream secrets changes via the Provider/Issuer and update the secrets that are managed by the operator.

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.

The customer should not have to manually change/delete the downstream crds when invalidating or rotating a secret in the upstream secrets manager. Instead, the admin should be able to update the secret in the secrets manager and:

1. if the secret is updated, there should be minimally an event notification pushed for impacted pods/workloads, or rolling updates should be performed to update the pods/workloads with the new secret/certificate
2. if the secret is invalidated, there should be an event notification pushed for mission critical workloads (so that they can be updated in a safe manner) or non-mission critical workloads with the invalidated (breached) secret should be killed.

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.

Acceptance criteria for the feature should be a release of this feature for each of the above mentioned operators. The workflow/process can be opinionated (i.e. Red Hat has developed what it believes is the right manner by which this should be achieved)

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>