Uploaded image for project: 'OpenShift Over the Air'
  1. OpenShift Over the Air
  2. OTA-611

Spike: Plan ClusterVersion history pruning

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • OTA 218

      Since way back, we've blindly pruned to 50 history entries, which can result in cluster_version{type="initial"} diverging from the actual, initial installed version. Because some things like install-time infrastructure depend on the initial version, we want to preserve that entry. This spike is about selecting:

      • Which history entries we would prefer to prune instead.
      • If we want to do something to the history data so that the presence of elided entries is explicit.
      • If we want to backport any of those changes, or just have them be 4.dev and later.

        1. rank.py
          2 kB
          W. Trevor King

              jottofar Jack Ottofaro (Inactive)
              trking W. Trevor King
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: