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

Allow custom pool configs to take priority over worker configs


    • MCO Sprint 244
    • 0
    • 0.0

      Due to alphanumeric ordering of the MCs, MCC-generated configs with pool names will get ordered such that worker configuration will generally take priority over custom pools, unless the custom pool name started with x,y,or z.


      This is mostly a problem for kubelet and containerruntimeconfigs. If the user wanted to create a kubeletconfig for base workers and then a special one for the custom pool, they are unable do easily do so.


      We should assume the user wants custom configs to take priority since all base worker configuration is otherwise inherited. Thus our MC merging logic should be updated to handle this.

            jerzhang@redhat.com Yu Qi Zhang
            jerzhang@redhat.com Yu Qi Zhang
            Sergio Regidor de la Rosa Sergio Regidor de la Rosa
            0 Vote for this issue
            1 Start watching this issue