Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-5504

Kogito Services CRDs are missing status fields in `get` commands

XMLWordPrintable

    • False
    • False
    • Undefined
    • 2022 Week 11-13 (from Mar 14), 2022 Week 14-16 (from Apr 4), 2022 Week 17-19 (from Apr 25), 2022 Week 20-22 (from May 16), 2022 Week 23-25 (from Jun 6), 2022 Week 26-28 (from Jun 27), 2022 Week 29-31 (from Jul 18), 2022 Week 32-34 (from Aug 8), 2022 Week 35-37 (from Aug 29), 2022 Week 38-40 (from Sept 19), 2022 Week 41-43 (from Oct 10), 2022 Week 44-46 (from Oct 31), 2022 Week 47-49 (from Nov 21), 2022 Week 50-02 (from Dec 12), 2023 Week 03-05 (from Jan 16)

      When one runs:

      oc get kogitoruntimes
      

      The output is something like:

      NAME                         REPLICAS   IMAGE                                                    ENDPOINT
      ks-kogito-order-processing   1          quay.io/ricardozanini/order-processing-workflow:latest   
      

      There's no information about the actual status of the resource, for example:

      oc get kogitosources
      NAME                      READY   REASON   SINK                                                        AGE
      kogito-order-processing   True             http://kogito-channel-kn-channel.kogito.svc.cluster.local   3h37m
      

      The columns `READY` and `REASON` give a hint to users about the actual status of the object. It's super valuable to admin/operators. Something like this needs to be added to the kubebuilder annotations:

      .status.conditions[?(@.type=='Ready')].status
      

              Unassigned Unassigned
              rhn-support-zanini Ricardo Zanini
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: