Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-108

Avoid workload disruption for GPG Public Key Rotation

XMLWordPrintable

    • Avoid workload disruption for GPG
    • False
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0

      Feature Overview and Background

      Changing any configuration (units, files, mirros, kube config etc) via the MCO will trigger a reboot for every node in the pool and some of those changes don't need a reboot.

      Problem

      Rebooting nodes on on-premise platforms during an MCO configuration rollout requires a significant amount of time (15m+, mainly in POST). A configuration done through the MCO is rotating GPG keys.

      Goals / Acceptance Criteria 

      • Avoid rebooting and drain in the cases of adding an GPG
      • Assess "backport-ability" to 4.7?

              mkenigsb@redhat.com Matthew Kenigsberg (Inactive)
              mkrejci-1 Michelle Krejci
              Rio Liu Rio Liu
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: