Ensure Chains works with the v1 version of TaskRuns and PipelineRuns

[jagathprakash]

Pipelines APIs have been updated to v1 from v1beta1.
Make sure that these versions work well with Chains.

Starting on the work here, made some issues to track the subtasks: Thanks @aaron-prindle !!

• [chains-v1.0.0] Convert Tekton v1 Object References Back to v1beta1 for backwards compatibility for Provenance Formatting #985
• [chains-v1.0.0] Convert incoming v1beta1 object to v1 before converting #986
• [chains-v1.0.0] [obsolete] Add a configMap option for the version that the Chains controller should watch (v1 or v1beta1). #987

[bendory]

Context: today chains is only watching v1beta1 pipelines:

• taskrun.Reconciler
• pipelinerun.Reconciler

[lcarva]

I wonder if it's possible for Chains to handle both v1beta1 and v1. That would facilitate adoption.

[bendory]

I wonder if it's possible for Chains to handle both v1beta1 and v1. That would facilitate adoption.

+1

In fact, we need a spin-off issue around handling cross-version compatibility with pipelines changes.

[vdemeester]

So, technically, as long as v1beta1 is served by tektoncd/pipeline, chains will work because the controller watches v1beta1 types, which are automatically converted, no matter how the user created them. This means that, today, if a user creates a v1 type, chains will handle it (because it will get it while watching v1beta1 objects).

I think, in a few release (most likely, more or less at the same time 0.47 gets release with a storage version change), chains should switch from watching v1beta1 to v1. This would make chains not working with older pipeline version (older than 0.43), but I think at some point this will be fine.

We may want to rename this issue to "switch chains controller to watch v1 types" instead 👼🏼

[bendory]

Immediate AIs:

• future releases of chains need to include release notes on compatibility with pipeline versions
• future releases of pipelines need to include release notes on compatibility with chains versions

TEP please:

• enhance chains and pipelines such that installation of a version incompatible with the existing installation would fail or at least alert to the problem

[vdemeester]

@bendory definitely +:100: on your checklist ❤️

[vdemeester]

/area roadmap