Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-59261

RHBoK never sets ReadyReplicas once operator is ready

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • OCP Node Sprint 274 (green)
    • 1
    • Done
    • Bug Fix
    • Hide
      Previously, the `ReadyReplicas` count was not set in the reconciler, which meant that the {product-title} Operator status would report that there were no replicas ready. With this release, the `ReadyReplicas` count is based on the number of ready replicas for the deployment, which ensures that the Operator shows as ready in the {platform} console when the `kueue-controller-manager` pods are ready.
      Show
      Previously, the `ReadyReplicas` count was not set in the reconciler, which meant that the {product-title} Operator status would report that there were no replicas ready. With this release, the `ReadyReplicas` count is based on the number of ready replicas for the deployment, which ensures that the Operator shows as ready in the {platform} console when the `kueue-controller-manager` pods are ready.
    • None
    • None
    • None
    • None

      In the operator spec, there is a field called ReadyReplicas. This reports the number of replicas that are ready.

      We never set this field in the reconciler so this leads to the operator status saying there are no replicas ready.

      This may impact the console in that the operator never shows the ready state.

      Right now, Customers have to verify that the operator is ready when the kueue-controller-manager and kueue-operator pods are all ready. This is subpar experience.

       

       

              skunkerk Sohan Kunkerkar
              rh-ee-kehannon Kevin Hannon
              None
              None
              Cameron Meadors Cameron Meadors
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: