Feature Overview (aka. Goal Summary)  

Workload identity is a key part of the zero-trust model. The SPIRE project aims to simplify the management and distribution of workload identities in the form of cryptographically verifiable identity documents. There is an increasing interest and uptake in this space within the Cloud native ecosystem.  The goal is to give customers a practical and scalable way to establish trust in a multi-cloud, multi-platform environment. It will strengthen OpenShift’s security capabilities and value-add as organizations harden their security policies. 

Goals (aka. expected user outcomes)

GA with seamless federation capabilities including

• .   OIDC Federation with EntraID IDP and workloads across cloud providers - On-prem, Azure, GCP and AWS -  [test only effort for GA]  
•     Spire<>Spire federation across OpenShift installs, including Cross-cloud Federation (AWS, GCP, Azure)  
•     BYO database (We validate with 1 version of PostGres. External DB management is via RH 3rd Party support policy. ACS Example  https://access.redhat.com/articles/7045053#database-scope-of-coverage-7) 

Stretch: 

• Spire Server install options with RH provided DR solutions    
• Tornjak for UI (TechPreview) 
• Upstream CA support

Requirements (aka. Acceptance Criteria):

Activity	Dependencies	Dependency contacts
Add support for Tornjak for enabling UI management, Federation relationships across clouds	Reviews by Auth experts in Control Plane team, IBM Research team for Tornjak enablement	IBM Research team(Mariusz Sabath Maia Iyer)

 __ 

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.

<To be added> 

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>