change apiVersion to rbac.authorization.k8s.io/v1 to support kfctl on ODH 1.4.0 and OCP 4.10

[shalberd]

fixes opendatahub-io/opendatahub-operator#187

apiVersion changes for roleBindings to be compatible with deployment via KfDef and version 1.4.0 of the operator on ODH 4.10

Description

openshift type notation led to errors when deploying manifests via KfDef.

How Has This Been Tested?

Made the changes in the PR, downloaded the 1.4.0 odh-manifests tar.gz, unpacked it, made changes locally, re-packed it, uploaded modified tar.gz to our server, then applied KfDef especially for Jupyter. On Openshift 4.10, with Operator 1.4.0. All roles, rolebindings, and clusterroles and clusterrolebindings are now present as they should be and the entire deployment is up and running.

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[openshift-ci]

Hi @shalberd. Thanks for your PR.

I'm waiting for a opendatahub-io 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.

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.

[LaVLaS]

/ok-to-test

[LaVLaS]

Thx for the fix. This worked for me

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LaVLaS

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:

• jupyterhub/OWNERS [LaVLaS]

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