New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Jupyter spawner Ui doesn't allow entering a custom image #2060
Comments
The decision to use HTML However, we believe it is crucial to allow users to specify custom Docker Images. We consider the following options:
We lean towards the second option, as it is more flexible and provides a better user experience. As a workaround for now, custom images can be specified in the If there are no objections on the proposed solution, we will come back with a PR to fix this issue. |
@jlewi we have already started the implementation of option 2, as described above. We will open a PR that should be ready for review very soon. |
* Add a radio button to enable users to select between 'standard' and 'custom' container images for their Jupyter Notebooks. Based on the checked option, the form dynamically switches between a dropdown list (standard images) and an input field (custom image). Closes kubeflow#2060 Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
* Add a radio button to enable users to select between 'standard' and 'custom' container images for their Jupyter Notebooks. Based on the checked option, the form dynamically switches between a dropdown list (standard images) and an input field (custom image). Closes kubeflow#2060 Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
@ioandr SGTM thanks |
Add a radio button to enable users to select between 'standard' and 'custom' container images for their Jupyter Notebooks. Based on the checked option, the form dynamically switches between a dropdown list (standard images) and a text input field (custom image). In order to disable custom user container images the admin user must set the image Spawner option as readOnly inside the corresponding `config.yaml` file. In this case, users will only be able to select a standard container image from the existing dropdown list, whose values are also specified in `config.yaml`. Closes kubeflow#2060 Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Add a radio button to enable users to select between 'standard' and 'custom' container images for their Jupyter Notebooks. Based on the checked option, the form dynamically switches between a dropdown list (standard images) and a text input field (custom image). In order to disable custom user container images the admin user must set the image Spawner option as readOnly inside the corresponding `config.yaml` file. In this case, users will only be able to select a standard container image from the existing dropdown list, whose values are also specified in `config.yaml`. Closes kubeflow#2060 Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Add a radio button to enable users to select between 'standard' and 'custom' container images for their Jupyter Notebooks. Based on the checked option, the form dynamically switches between a dropdown list (standard images) and a text input field (custom image). In order to disable custom user container images the admin user must set the image Spawner option as readOnly inside the corresponding `config.yaml` file. In this case, users will only be able to select a standard container image from the existing dropdown list, whose values are also specified in `config.yaml`. Closes kubeflow#2060 Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
* Reset Volumes and VolumeMounts before each API call Clean up previously appended Volumes and VolumeMounts before creating a new Notebook Pod in K8s. Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Allow custom container images in the JH Spawner UI Add a radio button to enable users to select between 'standard' and 'custom' container images for their Jupyter Notebooks. Based on the checked option, the form dynamically switches between a dropdown list (standard images) and a text input field (custom image). In order to disable custom user container images the admin user must set the image Spawner option as readOnly inside the corresponding `config.yaml` file. In this case, users will only be able to select a standard container image from the existing dropdown list, whose values are also specified in `config.yaml`. Closes #2060 Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Add basic server-side validation of config values Spawner option values marked as readOnly inside `config.yaml` have higher priority than user-specified form values and should be applied unchanged. Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Do not use Math.round() for Volume Size in Rok UI Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Add comments and examples in JH Spawner config files Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
* Reset Volumes and VolumeMounts before each API call Clean up previously appended Volumes and VolumeMounts before creating a new Notebook Pod in K8s. Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Allow custom container images in the JH Spawner UI Add a radio button to enable users to select between 'standard' and 'custom' container images for their Jupyter Notebooks. Based on the checked option, the form dynamically switches between a dropdown list (standard images) and a text input field (custom image). In order to disable custom user container images the admin user must set the image Spawner option as readOnly inside the corresponding `config.yaml` file. In this case, users will only be able to select a standard container image from the existing dropdown list, whose values are also specified in `config.yaml`. Closes kubeflow#2060 Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Add basic server-side validation of config values Spawner option values marked as readOnly inside `config.yaml` have higher priority than user-specified form values and should be applied unchanged. Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Do not use Math.round() for Volume Size in Rok UI Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com> * Add comments and examples in JH Spawner config files Signed-off-by: Ioannis Androulidakis <ioannis@arrikto.com> Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
With the new spawner UI, it doesn't look like we can enter a custom docker image. We can only select prebuilt images.
@ioandr @vkoukis is this a quick fix we can complete before 0.4?
The text was updated successfully, but these errors were encountered: