Openscapes hub image update

[betolink]

Context

At Openscapes we're using different Docker images to support R, Python and Matlab users, I thought there was a github action somewhere at 2i2c to detect when a new image has been pushed and opens a PR to update the hub config

We have a new image for Python openscapes/python:11de2c5 and we want to test it on staging (staging.openscapes.2i2c.cloud/) is it possible without deploying it to prod?

Is there a way to streamline these updates to the hub config? is the bot/github action only configured for the Python image? Thanks!

Proposal

No response

Updates and actions

No response

[sgibson91]

Hi @betolink You can use the configurator to test the image on staging without affecting prod. Docs are here: https://docs.2i2c.org/en/latest/admin/howto/configurator.html This is probably the quickest way for you to manage your image (it work on both staging and prod)

Using the configurator in this way does not update hub config, though it will always override what is listed in the hub config. Some folk find this confusing and we need to find some dev cycles to put into improving it I think 😕

infrastructure/.github/workflows/bump-image-tags.yaml

Lines 35 to 39 in b6ad29f

	# Bump images in openscapes cluster
	- name: "OpenScapes profiles"
	config_path: "config/clusters/openscapes/common.values.yaml"
	# Note: if position of images in profileList changes, update the index in these expressions
	images_info: '[{"values_path": ".basehub.jupyterhub.singleuser.profileList[0].profile_options.image.choices.python.kubespawner_override.image"}, {"values_path": ".basehub.jupyterhub.singleuser.profileList[0].profile_options.image.choices.rocker.kubespawner_override.image"}, {"values_path": ".basehub.jupyterhub.singleuser.profileList[0].profile_options.image.choices.matlab.kubespawner_override.image"}]'

This is how the action is configured to auto-bump your images, and they are looking at all three images. This action only runs weekly on Monday though, it is not triggered by pushing a tag to a Docker repository.

I think eventually, we would like to auto-populate a list of tags from a image repo, but that work is still ongoing #1253

[sgibson91]

Also, these kinds of questions are really good to send to [email protected] rather than opening an issue :)

[betolink]

Thanks for the info @sgibson9! Before opening the issue I used the configurator and had no effect on the spawned instance =(
I can follow up on the email.

[sgibson91]

Oh yes - sorry my bad. The configurator doesn't work for profile list options like you've got. Sorry for the false information on my part 🤦🏻‍♀️

This is some of the development we need to do to improve the configurator