Uploaded image for project: 'OpenShift Etcd'
  1. OpenShift Etcd
  2. ETCD-677

Configure removal of etcd container from static pod manifest

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.19
    • None
    • None
    • False
    • None
    • False
    • OCPSTRAT-1514 - Two node OpenShift cluster with fencing (2NO) - TP

      For 2NO we need to replace our currently running etcd after the installation with the one that is managed by pacemaker.

      This allows us to keep the following benefits:

      • installation can stay the way it is
      • upgrade paths are not blocked
      • we can keep existing operator functionality around (cert rotation, defrags etc)
      • pacemaker can control etcd without any other interference

      AC:

      • on a (later specified) signal, we roll out a static pod revision without the etcd container

              tjungblu@redhat.com Thomas Jungblut
              tjungblu@redhat.com Thomas Jungblut
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: