Epic Goal*

As a user, I would like to separate the generation and rollout of separate generation and rollout of secrets/next-bound-service-account-signing-key.

 
Why is this important? (mandatory)

This is necessary to a) ensure the newly generated private key never leaves the cluster, while b) add the newly generated public key to an external OIDC prior to the cluster using it. Specifically, this is needed for a clusters in "Manual/STS" mode in order to update the key's without causing an outage to the core operators and/or user workloads that rely on the cloud provider OIDC integration.
 
Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. https://github.com/openshift/cloud-credential-operator/blob/master/docs/rotate-oidc-key.md
2. https://access.redhat.com/articles/regenerating_cluster_certificates

 
Dependencies (internal and external) (mandatory)

What items must be delivered by other teams/groups to enable delivery of this epic. 

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - 
• Documentation -
• QE - 
• PX - 
• Others -

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

Drawbacks or Risk (optional)

Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”