Channel broker controller uses v1alpha1 broker and trigger types

[grantr]

Describe the bug
The channel broker still uses the v1alpha1 types to work with brokers and triggers.

Expected behavior
The channel broker uses v1beta1 types.

Knative release version
0.14.0

Additional context
I'm not sure if this is actually causing any issues, but it seems like it could theoretically cause failed trigger updates since the trigger validation in v1beta1 is different.

Actually that might be a reason to continue using the v1alpha1 types if the v1alpha1 validation is stricter. So maybe this can be closed if it's working as intended:tm:.

[vaikas]

This is in the reconcilers?

[grantr]

Yes:

eventing/pkg/reconciler/broker/broker.go

Lines 42 to 49 in a5df82a

	duckv1alpha1 "knative.dev/eventing/pkg/apis/duck/v1alpha1"
	"knative.dev/eventing/pkg/apis/eventing"
	"knative.dev/eventing/pkg/apis/eventing/v1alpha1"
	messagingv1beta1 "knative.dev/eventing/pkg/apis/messaging/v1beta1"
	clientset "knative.dev/eventing/pkg/client/clientset/versioned"
	brokerreconciler "knative.dev/eventing/pkg/client/injection/reconciler/eventing/v1alpha1/broker"
	eventinglisters "knative.dev/eventing/pkg/client/listers/eventing/v1alpha1"
	messaginglisters "knative.dev/eventing/pkg/client/listers/messaging/v1alpha1"

[vaikas]

#3066
Let's just hold off on this work until 0.16 for Broker. In 0.15 we can reconcile Triggers using v1beta1.

[vaikas]

Ok, triggers are now being reconciled with v1beta1:
#3093

[matzew]

@vaikas @grantr - see #3238

[grantr]

We don't have the v1alpha1 types anymore, so this can be closed