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

Priority Order Change for merging MachineConfigs

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • None
    • OS
    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • Program Call

      Feature Overview (aka. Goal Summary)  

      The MCO merges MachineConfigs in alphanumerical order. Because all custom pools also are workers, this effectively means that all "worker" configs will take precedence over custom pools that come earlier in alphabetic order. This is counter to most expectations where the reason for creating the custom pool is in order to be different than the worker pool.

      Goals (aka. expected user outcomes)

      Custom pool configs will "win" over worker configs. This is inline with what most customers expect.

            rhn-support-mrussell Mark Russell
            rhn-support-mrussell Mark Russell
            Matthew Werner Matthew Werner
            Derrick Ornelas Derrick Ornelas
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: