Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-193

Automatically restart storage operators pods when the CA certificates are updated


    • False
    • Hide


    • False
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0

      Feature Overview (aka. Goal Summary)  

      The storage operators need to be automatically restarted after the certificates are renewed.

      From OCP doc "The service CA certificate, which issues the service certificates, is valid for 26 months and is automatically rotated when there is less than 13 months validity left."

      Since OCP is now offering an 18 months lifecycle per release, the storage operator pods need to be automatically restarted after the certificates are renewed.

      Goals (aka. expected user outcomes)

      The storage operators will be transparently restarted. The customer benefit should be transparent, it avoids manually restart of the storage operators.


      Requirements (aka. Acceptance Criteria):

      The administrator should not need to restart the storage operator when certificates are renew.

      This should apply to all relevant operators with a consistent experience.


      Use Cases (Optional):

      As an administrator I want the storage operators to be automatically restarted when certificates are renewed.


      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.


      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.



      This feature request is triggered by the new extended OCP lifecycle. We are moving from 12 to 18 months support per release.


      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.


      Documentation Considerations

      No doc is required


      Interoperability Considerations

      This feature only cover storage but the same behavior should be applied to every relevant  components. 

            rh-gs-gcharot Gregory Charot
            rh-gs-gcharot Gregory Charot
            Maxim Patlasov Maxim Patlasov
            Penghao Wang Penghao Wang
            Lisa Pettyjohn Lisa Pettyjohn
            Maxim Patlasov Maxim Patlasov
            Gregory Charot Gregory Charot
            Eric Rich Eric Rich
            0 Vote for this issue
            4 Start watching this issue