Round 1: Subscription Controller

[evankanderson]

Write a controller for Subscriptions. This should:

1. Resolve all object references to DNS names.
2. Fill out ChannelSubscriberSpec on the from field of the Channel.
3. Update Status based on the success of first release #1 and Added collaboration document link #2

[neosab]

/assign neosab

I would like to help here

[evankanderson]

@vaikas-google and/or @grantr are probably good resources on how this should look.

Additional deliverables:

4. Test coverage > 80%
5. Deployment which runs the Subscription controller
6. Minimal RBAC rules for 5 (probably cluster viewer + update on Channel)

[neosab]

I didn't realize #437 was posted a little earlier. I will try to contribute what I can in addition to that.

[neosab]

@evankanderson on # 5 - I was under the impression that the Subscription controller will run within the main eventing-controller deployment. That's not the idea?

[vaikas]

it runs in the eventing-controller, unless there's a good reason not to that I'm not aware of.

[neosab]

/unassign neosab