Remove role & rolebinding configuration for in-memory-channel-dispatcher

[sravankumar777]

Fixes #
Duplicated role & rolebinding configuration for in-memory-channel-dispatcher.

Proposed Changes

During the deployment of knative-eventing with release yaml of v0.8.0, deployment file has ClusterRole & Role information duplicated for in-memory-channel-dispatcher.

eventing/config/provisioners/in-memory-channel/in-memory-channel.yaml

Lines 187 to 220 in a59dae6

	apiVersion: rbac.authorization.k8s.io/v1
	kind: Role
	metadata:
	name: in-memory-channel-dispatcher
	namespace: knative-eventing
	labels:
	eventing.knative.dev/release: devel
	rules:
	- apiGroups:
	- ""
	resources:
	- "configmaps"
	verbs:
	- get
	- list
	- watch
	---
	apiVersion: rbac.authorization.k8s.io/v1
	kind: RoleBinding
	metadata:
	name: in-memory-channel-dispatcher
	namespace: knative-eventing
	labels:
	eventing.knative.dev/release: devel
	subjects:
	- kind: ServiceAccount
	name: in-memory-channel-dispatcher
	namespace: knative-eventing
	roleRef:
	kind: Role
	name: in-memory-channel-dispatcher
	apiGroup: rbac.authorization.k8s.io

Release Note

Upcoming release for knative-eventing should be included with **in-memory-channel-dispatcher** cluster role & cluster role binding. 

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sravankumar777
To complete the pull request process, please assign n3wscott
You can assign the PR to them by writing /assign @n3wscott in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[knative-prow-robot]

Hi @sravankumar777. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[sravankumar777]

@googlebot I signed it!

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[sravankumar777]

@googlebot I fixed it.

[matzew]

@sravankumar777 this file is gone, since:

#1484

[matzew]

/close

[knative-prow-robot]

@matzew: Closed this PR.

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.