add cherrypicker deployment in bazel prow configuration

[droslean]

In effort of solving #23469

Signed-off-by: Nikolaos Moraitis nmoraiti@redhat.com

[droslean]

/hold

I am not sure if this is enough to deploy cherrypicker.

[alvaroaleman]

/cc @chaodaiG @cjwagner @mpherman2

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chaodaiG, droslean

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/prow/cluster/OWNERS [chaodaiG]

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

[chaodaiG]

I think this is all what we need for deploying cherrypicker in prow.k8s.io, it doesn't need RBAC right?

[droslean]

I think this is all what we need for deploying cherrypicker in prow.k8s.io, it doesn't need RBAC right?

Regarding the way that external-plugins work, they shouldn't need any special RBACs if they don't directly access a resource in the cluster. I think in cherrypicker case it doesn't need any.

Feel free to hold cancel, once you confirm this.

[alvaroaleman]

No it doesn't need rbac, it just talks to github
/hold cancel