We have decided to manage tags like this:
the last 2 versions of python
the last 2 versions of r
the last 2 versions of spark
then for example we could have a tag that gives:
-> tag free or YYYYMMDD should generate with inputs
-> python 3.9, 3.10
-> r 4.3,4.4
-> spark 3.2.2,3.3.0
image should name for example python3.9-spark3.2.0-YYYYMMDD and all cartesian product for images.
image with no python, r, spark should have tag YYYYMMDD.
The build could be launch each week on this tag for new releases.
The propagation on the catalog could be automate with renovate (or with renovate and github workflow) as the catalog yaml values.schema.json could be tricky.
We have decided to manage tags like this: the last 2 versions of python the last 2 versions of r the last 2 versions of spark
then for example we could have a tag that gives:
-> tag free or YYYYMMDD should generate with inputs -> python 3.9, 3.10 -> r 4.3,4.4 -> spark 3.2.2,3.3.0
image should name for example python3.9-spark3.2.0-YYYYMMDD and all cartesian product for images. image with no python, r, spark should have tag YYYYMMDD.
The build could be launch each week on this tag for new releases.
The propagation on the catalog could be automate with renovate (or with renovate and github workflow) as the catalog yaml values.schema.json could be tricky.