Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-1565

Inconsistency in labeling Tkn cluster tasks

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • Pipelines 1.5
    • Pipelines 1.5
    • Tekton Catalog
    • None

      • Now with pipelines1.5 release we are officially supporting tkn image
      --- tkn ---
"default": "registry.redhat.io/openshift-pipelines/pipelines-cli-tkn-rhel8@sha256:25aa37d4f600d9c060d11d4dd19ce852fe074c0004d010d0c35af11f0fc4cae2",
--- tkn-1-5-0 ---
"default": "registry.redhat.io/openshift-pipelines/pipelines-cli-tkn-rhel8@sha256:25aa37d4f600d9c060d11d4dd19ce852fe074c0004d010d0c35af11f0fc4cae2",

      I see difference in labeling both cluster tasks.
      tkn is marked as community supported but actually it should be redhat.
      Expected: Tkn cluster task has to be labeled `operator.tekton.dev/provider-type=community` to maintain consistency.

      oc get clustertasks --show-labels -o wide| grep -i tkn                                     
tkn                        13m   app.kubernetes.io/version=0.2,operator.tekton.dev/provider-type=community
tkn-1-5-0                  13m   app.kubernetes.io/version=0.2,operator.tekton.dev/provider-type=redhat

            rh-ee-nikthoma Nikhil Thomas
            pthangad Praveen Kumar Reddy Thangadancha (Inactive)
            Praveen Kumar Reddy Thangadancha Praveen Kumar Reddy Thangadancha (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: