Add BuildConfiguration objects to build RStudio and CUDA R RStudio notebooks oc OCP cluster

[atheo89]

This PR fixes:
https://issues.redhat.com/browse/RHOAIENG-1478
https://issues.redhat.com/browse/RHOAIENG-315

This pull request introduces two BuildConfig objects, enabling users to create an RStudio Workbench on their cluster.
The branch that hosts the RStudio dockerfile is hosted on f/rstudio-rhel9 branch

Probably a good enhancement on this implementation is to, have prebuild the base-rhel9 image in order to avoid its build all the time. This enchancment has already stated on this PR: #123 However, this implementation it stand alone as is now.

How has been Tested

There are two ways to deploy the new Build Configs

The first and the recommended is (Deploy the configs outside from RHOAI):

1. Login on the cluster:
   oc login <ocp cluster url>

2. Enter on redhat-ods-applications namespace if you use RHOAI or opendatahub if you use ODH
   oc project redhat-ods-applications

3. Create a secret, PM me to provide you testing credentials:
   oc create secret generic rhel-subscription-secret --from-literal=USERNAME=<username> --from-literal=PASSWORD=<pass> --from-literal=BASEURL=<baseurl> --from-literal=SERVERURL=<serverurl> -n redhat-ods-applications

4. Run the rstudio-buildconfig.yaml file to to deploy the simple version of RStudio:
   oc apply -f rstudio-buildconfig.yaml -n redhat-ods-applications
   Or run the cuda-rstudio-buildconfig.yaml to build the CUDA version of RStudio:
   oc apply -f cuda-rstudio-buildconfig.yaml-n redhat-ods-applications

5. After creating all the objects, navigate to the BuildConfig and initiate the build process as illustrated in the image:

6. Once the builds are complete means that the RStudio workbench is ready
   

7. To add Workbench to the list of notebooks, start by obtaining the image from the rstudio-rhel9 Image Stream and importing it as a custom notebook, following the instructions in the image below:
   

8. Spin up the workbench that you just created
   

The second way is (Deploy the configs inside RHOAI, as it is implemented already):

1. Edit the DSC of the operator with the following:

    workbenches:
      devFlags:
        manifests:
          - contextDir: components/odh-notebook-controller/config
            sourcePath: ''
            uri: 'https://github.com/opendatahub-io/kubeflow/tarball/v1.7.0-5'
          - contextDir: components/notebook-controller/config
            sourcePath: ''
            uri: 'https://github.com/opendatahub-io/kubeflow/tarball/v1.7.0-5'
          - contextDir: ''
            sourcePath: base
            uri: >-
              https://github.com/red-hat-data-services/notebooks/tarball/pull/118/head

2. Create a secret, PM me to provide you testing credentials:
   oc create secret generic rhel-subscription-secret --from-literal=USERNAME=<username> --from-literal=PASSWORD=<pass> --from-literal=BASEURL=<baseurl> --from-literal=SERVERURL=<serverurl> -n redhat-ods-applications

3. Follow the same steps from (5) till the end

[jiridanek]

What's RHOAI 2.7 going to do? The second option? So when I install the Operator, it will automatically deploy the buildconfigs for me, so I then need to create rhel-subscription-secret, and trigger the build?

[harshad16]

Based on the discussions, we can perhaps include additional details on the imagestream, so user can directly use these in the RHOAI dashboard

PTAL at suggestions

[atheo89]

Created this PR #127 with two fixes on the CUDA Dockerfile

[harshad16]

Created this PR #127 with two fixes on the CUDA Dockerfile

@atheo89 , if we switch to ARG, then we might have to pass in the buildarg on buildconfig:https://docs.openshift.com/container-platform/3.11/dev_guide/builds/build_strategies.html#docker-strategy-build-args
however, i think buildconfig, buildarg doesn't support secrets yet.
https://access.redhat.com/solutions/4501551

[atheo89]

if we switch to ARG, then we might have to pass in the buildarg on buildconfig:https://docs.openshift.com/container-platform/3.11/dev_guide/builds/build_strategies.html#docker-strategy-build-args however, i think buildconfig, buildarg doesn't support secrets yet. https://access.redhat.com/solutions/4501551

I will add ENVs on the Dockerfiles as it was

[harshad16]

/lgtm
/approve

thanks for the work 💯

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harshad16

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:

• OWNERS [harshad16]

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