Feature Overview (aka. Goal Summary)  

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

 ----- copied from RFE-8386 -----
Who is the customer behind the request?

Telco.

What is the nature and description of the request?

The customer needs to securely hydrate a custom resource from information stored in Hashicorp Vault. The External Secrets Operator has an implementation for just this feature in code review. We need to prioritize completion of the implementation, and a Red Hat supported operator release.

Why does the customer need this? (List the business requirements here)

The customer is in a highly regulated environment, and needs to configure a CoreOS user password hash using a machine config. This password hash cannot be stored in git. And they would like a general facility for securely sync'ing other custom resources from Vault in the future.

The customer has been considering use of the Argo CD Vault plugin. However, the Argo CD project discourages the use of Argo CD plugins now due to performance impacts and implementation complexity, and the customer strongly prefers a supported solution.

How would the customer like to achieve this? (List the functional requirements here)

Using the ESO Sync Custom Resources implementation.

For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

An appropriate test would be to specify an ExternalSecret to create a machine config that sets a user's (e.g. the `core` user's) password hash.

Does the customer have any specific timeline dependencies and which release would they like to target?

ASAP, or January 2026, if possible. Next generation mobile core infrastructure is being implemented and replacing the workaround before going to customer production is important.
 ------------------------------------------------------

<your text here>

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.

 This Feature was generated in OCPSTRAT via acceptance of RFE-8386. Ensure the stated Acceptance Criteria below will fulfill the needs specified in the RFE.

<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>