Only cache pods and taskruns with the buildrun label

[SaschaSchwarze0]

Changes

When we create a TaskRun for a BuildRun, then we always add the buildrun.shipwright.io/name label. Tekton also applies this to the pod it creates.

This change configures the cache of our manager to only cache TaskRuns and Pods that have this label. This should bring down the memory usage of our controller a lot, especially when it runs in a cluster that is used for not just Shipwright and has many pods and maybe also taskruns which are not applicable. It may also improve startup time. In my local home cluster, "just" 391 pods and 258 taskruns in total where for each only 25 are BuildRun-related, the memory usage after startup went down from 33 MB to 20 MB.

I had to move up the scheme registration to before initializing the manager to pass it in as the manager needs it for the cache configuration.

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

Improve resource consumption by only caching shipwright-related taskruns and pods

[dorzel]

This LGTM - I'm assuming the cache behavior before was to cache all pods and TaskRuns on the cluster? If so, it makes sense to only cache what we care about for the controller.

[qu1queee]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qu1queee]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment