Add instructions for creating a Custom Notebook Image

[theckang]

Created a section for creating custom notebook images and uploading them to RHOAI for new workbenches
Added example instructions for how-to on a Minimal Python notebook base image

[codekow]

@theckang Will you update this to use a build config and avoid using podman?

[codekow]

@theckang Here are some old examples you can un-suck. 😄

https://github.com/codekow/s2i-patch/blob/main/openshift/build-s2i-ms-odbc-17.yml
https://github.com/codekow/s2i-patch/tree/main/s2i-ms-odbc-17

[codekow]

@theckang See comments

[theckang]

@theckang Will you update this to use a build config and avoid using podman?

great idea, give me a few cycles to update

[theckang]

@codekow PR updated, podman removed

[codekow]

@theckang

I like the changes

What do you think about the following use cases:

• Embeding the Containerfile in the build config (avoid any local tooling, modify only in the OCP console)?
  • In addition or in place of the local oc new-build?
• Showing a (forked) external repo containing artifacts (this seems like it might be too much to me)

[theckang]

@theckang

I like the changes

What do you think about the following use cases:

• Embeding the Containerfile in the build config (avoid any local tooling, modify only in the OCP console)?

  • In addition or in place of the local oc new-build?

• Showing a (forked) external repo containing artifacts (this seems like it might be too much to me)

Ideally - the user would fork the official notebook repo: https://github.com/red-hat-data-services/notebooks/tree/main/jupyter/minimal

And push Pipfile / Containerfile changes up and then launch a build off their fork.

This would require adding a bunch of Git commands and working with GitHub outside the terminal.

We could have a repo containing all the artifacts in advance, but I personally don't think the user would learn anything. I wanted to force the Containerfile creation and the Pipfile modifications to show how to make changes.

We could embed the Containerfile but there is still the Pipfile (and the associated pipenv lock) that is part of the build. I think if we wanted to bundle that as part of the build, the BYO-fork-repo is the right approach.

[codekow]

@theckang LGTM

[codekow]

@theckang You good with merging this?

[theckang]

got ask @dmarcus-wire as he wanted to see file restructuring - ready to merge?