Remove PipelineResource support

[wlynch]

PipelineResources have been deprecated from Pipelines for quite some time now (https://github.com/tektoncd/pipeline/blob/main/docs/deprecations.md#deprecation-table says since Dec 2021) - we should be safe to rip this out from Chains.

[wlynch]

Heads up - Pipelines was still allowing creation of PipelineResources via v1beta1 through v0.45.0, so it's very likely that there's still usage of Pipeline Resources for recent clients.

Support was removed in v0.46.0, but the API types were removed as well so this breaks our ability to safely watch older Tekton versions if we update our client version to v0.46.0 😭

I reached out on the Pipelines PR to ask to roll back the client changes.

[chuangw6]

After creating #764 to remove it, I just realized this ticket. Thanks for creating this ticket.

Should we remove support for the pipelineresources in Chains? I feel like if we don't remove it, users who use the combo of pipeline >= v0.46 and chains >= 0.16 will have trouble.

[lcarva]

Should we remove support for the pipelineresources in Chains? I feel like if we don't remove it, users who use the combo of pipeline >= v0.46 and chains >= 0.16 will have trouble.

Good question. According to this, the pipeline release v0.44.0 is still supported until Jan 24, 2024. So maybe we should until then?

[wlynch]

I'd like to keep compatibility with current supported pipeline LTS versions, unless there's a good reason we can't.

We got the resources API change reverted in tektoncd/pipeline#6436 - if/when pipeline releases v0.46.1 we should be able to upgrade with compatibility.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.