Round 1: In-Memory Channel Controller

[evankanderson]

Write a controller for In-Memory Channels and Provisioners. This should:

1. Create the Provisioner/update the Status
2. Define required fields (if any) in Channel arguments.
3. Copy configuration from Channel CR to delivery implementation (Round 1: In-Memory Channel Delivery #439)
4. Update Status based on the success of 3
5. Test coverage > 80%
6. Deployment which runs the Subscription controller
7. Minimal RBAC rules for 5 (probably cluster viewer + update on Channel)

[n3wscott]

I wonder, should we implement this assuming it will be out of repo?

[grantr]

I'd like to take a stab at this if nobody else is already working on it or planning to.

@n3wscott I think implementing this out of repo would be a good test case for the feasibility of 3rd-party implementations, though it might slow the process down a bit. I can't decide if it's worth delaying the first prototype to gain that knowledge now.

[grantr]

@adamharwayne is expecting to do this as part of his sidecar work.

[n3wscott]

/assign @adamharwayne

[evankanderson]

/close

Fixed by #484

[knative-prow-robot]

@evankanderson: Closing this issue.

Details

In response to this:

/close

Fixed by #484

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.