Uploaded image for project: 'OpenShift API Server'
  1. OpenShift API Server
  2. API-1603

Fallback (Protocol) for Emergency Certificate Rotation

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Critical
    • None
    • openshift-4.13
    • kube-apiserver
    • Fallback (Protocol) for Emergency Certificate Rotation
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 50
    • 50% 50%

    Description

      https://docs.google.com/document/d/198C4xwi5td_V-yS6w-VtwJtudHONq0tbEmjknfccyR0/edit#heading=h.oynu7bkhz613

       

      Goal:

      • recover the cluster when certs expire while a node is down
      • should work for OpenShift (both HA and Single)
      • Ideally, if possible, we want to make it an automated repair process. 
      • cover both rebooted node and suspended node
      • Evaluate (during the research) effort to provide a mechanism to the admin so he/she can trigger a cert regeneration

       

      Non Goal:

      • change host name / node identity
      • make rotation faster
      • any existing cert we have today should not have modified expiration period

       

      Acceptance Criteria:

      • documentation with findings
      • OpenShift KEP 

      Attachments

        Issue Links

          Activity

            People

              dgrisonn@redhat.com Damien Grisonnet
              dgrisonn@redhat.com Damien Grisonnet
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated: