Introduce a reusable Kind pipeline / task for testing

[ghost]

Feature request

Over in the Tekton Results project, @wlynch has introduced Kind as part of e2e testing. The task definition is here and the runner script is here.

It could be really useful to apply Kind to our testing more broadly. For example, we could create kind clusters for checking behaviour with feature-flags on / off without incurring the overhead of spinning up completely fresh GKE clusters for each configuration.

This issue is for tracking work towards that goal: introduce a Task or Pipeline that is reusable across projects and can be used to boot up a Kind cluster and run tests.

[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.

[afrittoli]

Work in that direction: #927

[afrittoli]

/lifecycle frozen This is being worked on

[vdemeester]

/lifecycle frozen

[lbernick]

@afrittoli @vdemeester can this be closed now that we have the Kind catalog Task?

[dibyom]

/assign @abayer