A lightweight, multi-tenant, scalable and secure gateway that enables Jupyter Notebooks to share resources across distributed clusters such as Apache Spark, Kubernetes and others.
As discussed in #1127, there is currently no way to easily enable dynamic kernelspec additions to containerized deployments because the deployment scripts always specific kernelspec entries. Since dynamic kernelspec additions are default behaviors (when kernelspecs are not explicitly listed in the configuration), we should enable similar support in containerized deployments. This pull request enables that functionality.
The start-enterprise-gateway.sh that is the CMD in the enterprise-gateway image has been modified to detect if the EG_KERNEL_WHITELIST env has a value of null. When that value is detected, the --KernelSpecManager.whitelist command-line option is omitted, thereby exposing all kernelspecs configured into the image. It is presumed that deployments wishing to dynamically add kernelspec definitions have mounted the /usr/local/share/jupyter/kernels directory (or otherwise made its update available). Updates made to that directory will be automatically picked up when kernelspecs are refreshed.
A value of null was used for EG_KERNEL_WHITELIST to make this determination because that is the value Helm will set when the whitelist: entry of the values.yaml has no entries. This allows operators to easily remove (or comment out) all existing kernelspec entries to enable this functionality.
As discussed in #1127, there is currently no way to easily enable dynamic kernelspec additions to containerized deployments because the deployment scripts always specific kernelspec entries. Since dynamic kernelspec additions are default behaviors (when kernelspecs are not explicitly listed in the configuration), we should enable similar support in containerized deployments. This pull request enables that functionality.
The
start-enterprise-gateway.shthat is theCMDin the enterprise-gateway image has been modified to detect if theEG_KERNEL_WHITELISTenv has a value ofnull. When that value is detected, the--KernelSpecManager.whitelistcommand-line option is omitted, thereby exposing all kernelspecs configured into the image. It is presumed that deployments wishing to dynamically add kernelspec definitions have mounted the/usr/local/share/jupyter/kernelsdirectory (or otherwise made its update available). Updates made to that directory will be automatically picked up when kernelspecs are refreshed.A value of
nullwas used forEG_KERNEL_WHITELISTto make this determination because that is the value Helm will set when thewhitelist:entry of thevalues.yamlhas no entries. This allows operators to easily remove (or comment out) all existing kernelspec entries to enable this functionality.Resolves: #1127