Migrate Integration Tests to use kind + Prow

[chitrangpatel]

Migrate integration tests to used a kind cluster.
We should stop using GKE clusters directly for tests unless really required for some reason.

• pipelines
• triggers Migrate Triggers e2e test to kind #1252
• Chains:
  - uses kind for smoke e2e tests against different k8s versions
  - not sure if there are any non-kind e2e tests @wlynch @priyawadhwa
• Results:
  - I think results started using kind from the beginning @wlynch
• Dashboard: Move Dashboard integration tests from GKE to Kind #1191
• CLI:
  - I'm not sure if there is any e2e tests that creates a cluster. @vdemeester @chmouel ?
  - Prepare setup for moving e2e to kind cli#2259
• Catalog: TBD - maybe as part of the migration?
• Experimental: TBD - maybe as part of the migration?

We might want to create repo specific issues where required.

[abayer]

Pipeline's already moved, and I know @dibyom has been working on this for Triggers, but I don't know the status there.

[chitrangpatel]

/priority important

[tekton-robot]

@chitrangpatel: The label(s) priority/important cannot be applied, because the repository doesn't have them.

In response to this:

/priority important

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.

[chitrangpatel]

/priority importantsoon

[tekton-robot]

@chitrangpatel: The label(s) priority/importantsoon cannot be applied, because the repository doesn't have them.

In response to this:

/priority importantsoon

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.

[chitrangpatel]

/priority important-soon

[AlanGreene]

Dashboard is already done since ~August/September

edit: #1191

[vdemeester]

/area roadmap

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

[AlanGreene]

/lifecycle frozen