Expected Behavior

While looking into #19 we've decided that for now we want to move forward without kubebuilder (watch #19 for more info re. the rationale) (we might revisit this later afte rfollowing up with kubebuidler folks).

So we would like:

• build-pipeline's controllers to no longer require kubebuilder
• Any boilerplate added by kubebuilder that we don't want anymore to be removed
• Basic skeletons of these controllers to be re-added, but implemented in the same style as the knative/serving and knative/build controllers
• We should maintain approximately the same level of functionality we currently have, i.e. it is possible to run controllers for all CRDs and perform some very basic validation against them.

We may still want to keep using envtest if it can work without our controllers using controller-runtime, since it's pretty handy to be able to run the controllers in tests without a k8s cluster.

Actual Behavior

Our current controllers were built using kubebuilder v1 and depend on controller-runtime.

Additional Info

See #19 for more.