Custom Kernel Images loading on Enterprise Gateway #976
-
Hello Team, I have built a custom Kernel Image for EG and pushed it to docker.io My objective is to launch Enterprise Gateway with my custom kernel. When I try to install it via Helm, I am seeing the issue that the Kernel spec volume mount not found.
Here is a snippet from my values.yaml file that I have used to launch the EG. **kernel: kernelspecs: Here is my deployment.yaml **apiVersion: apps/v1 I know documentation is scarce hoping someone would advise what am I missing here. Best Regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @j-raghavan. Are you able to launch any of the out-of-the-box kernel images that come configured with EG? I would focus on getting It looks like the image you created ( Two things must occur for a custom kernel image to be used.
For starters, besides making sure the basics are working in your configuration, you might want to create an appropriate init-container where the kernel specifications are located in |
Beta Was this translation helpful? Give feedback.
Hi @j-raghavan. Are you able to launch any of the out-of-the-box kernel images that come configured with EG? I would focus on getting
python_kubernetes
working in a similar configuration to what you are targeting if you haven't done so already.It looks like the image you created (
docker.io/mrjayasimha/jupyt3r_eg_kernel:0.1.0
) is intended to be an init-container containing all of your kernelspec references by virtue of it being referenced in the values yaml as thekernelspecs.image
. This kind of image merely houses kernel specifications - similar to what you find in the EG container under/usr/local/share/jupyter/kernels
and is not considered a "kernel image".Two things must occur for a …