Buses should report channel and subscription provisioning status

[scothis]

Expected Behavior

The Channel and Subscription resources should report status for whether the bus was able to provision the resource on the underlying infrastructure.

Actual Behavior

The Channel resource contain status conditions from the controller that sets up networking to the bus, but has no status indicating the bus is able to handle traffic sent to it for the channel. There are events for the channel and subscription reported by the bus, but these are not reflected in the status.

Additional Info

There are two concerns that need to be managed appropriately by a solution:

1. the bus will need rbac access to update the resource 🙁
2. the bus and controller must avoid race conditions when simultaneously updating the status 🙁🙁

CRD sub-resources will make this much easier.

[n3wscott]

I ran into something that this could have helped debug my issue today. I did not have a ClusterBus, but I did have a Bus named stub and it was reacting to subscriptions, BUT it was not seeing the channel because the channel was on a missing clusterbus and the subscription was not caring

[scothis]

Looks like this was attempted in #130, but the monitor and controller are in a race that leaves the status conditions out of sync.

[scothis]

The integration tests are currently failing because the channel statues never gets to ready

/assign @scothis

[scothis]

/close

[knative-prow-robot]

@scothis: Closing this issue.

Details

In response to this:

/close

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.