This PR allows a specific version of the egeria-jupyer-notebooks repository to be checked
out when the jupyter container is launched. this is defined in the yaml for the jupyter deployment.
A tag or branch can be specified by setting 'jupyter.gitTagForNotebooks'. If no value is specified, the the default branch (main) will be used.
In the chart values, the default value for this parm is set to: "main"
So for example, if we wanted to use the 'v313test' tag we'd deploy the chart with:
The jupyter image has increased in size (+200MB) -- see https://cloud.redhat.com/blog/jupyter-on-openshift-part-6-running-as-an-assigned-user-id for some of the hoops needed to get jupyter working well in openshift. as that article asserts, we are nearing the end of where we can customize the image - beyond this it needs recreating from scratch. This will not be done at this point
Signed-off-by: Nigel Jones nigel.l.jones+git@gmail.com
This PR allows a specific version of the egeria-jupyer-notebooks repository to be checked out when the jupyter container is launched. this is defined in the yaml for the jupyter deployment.
A tag or branch can be specified by setting 'jupyter.gitTagForNotebooks'. If no value is specified, the the default branch (main) will be used.
In the chart values, the default value for this parm is set to: "main"
So for example, if we wanted to use the 'v313test' tag we'd deploy the chart with: