Description of problem: The OpenShift Pipelines operator installs the TektonConfig CustomResourceDefinition with the follwing version number labels: ``` operator.tekton.dev/release=v1.6.0 version=v1.6.0 ``` This conflicts with the upstream Tekton operator version scheme. The Shipwright operator uses the CRD's version label to determine if it can deploy Tekton. Version-Release number of selected component (if applicable): 1.6 How reproducible: Always Steps to Reproduce: 1. Install the OpenShift Pipelines operator on OpenShift using OLM. 2. Observe the labels on the TektonConfig CRD Actual results: The version numbers in the labels correspond to the downstream OpenShift pipelines version. Expected results: One of the labels reports the compatible Tekton version of the operator. `operator.tekton.dev/release` might be the better fit. Additional info:
> One of the labels reports the compatible Tekton version of the operator. `operator.tekton.dev/release` might be the better fit. I think this could be a good way to handle this. I shall discuss it with my and get back to you
This is fixed in the latest releases, please let us know if that's not the case!