docs: Migrate example image defaults to release registry - #67
Merged
Merged
Conversation
tmvfb
marked this pull request as ready for review
September 28, 2026 09:28
tmvfb
marked this pull request as draft
September 28, 2026 11:22
tmvfb
changed the title
Korel
marked this pull request as ready for review
September 28, 2026 14:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
prokube-internal/prokube-customerto immutable release tags:europe-west3-docker.pkg.dev/prokube/releases/<image>:v1.0.0mobile-price-classification, is switched toreleases/...:v1.0.0in Automation/notebook ci #56 (which also adds theCOMPONENTS_IMAGEoverride there), so this PR leavespipeline.pyuntouched to avoid a merge conflictprokube/developmentdeletes images older than six months, so defaults pointing there would eventually break;prokube/releaseshas immutable tags and nolatestmolecules.yamlworkflow (itsimages/moleculessource was removed in 11a4eaf)Follow-up to #66.
Release images
The
v1.0.0images were copied withcrane copy --no-clobberfrom existing builds (digests preserved), as allowed for migration by RFC-006:minimal-mnistcommit-a44a4b4sha256:be7d3172…streamlit-examplecommit-a44a4b4sha256:433c7eae…minimal-custom-kserve-predictorcommit-a44a4b4sha256:35a69047…minimal-predictorcommit-a44a4b4sha256:e164737d…minimal-transformercommit-a44a4b4sha256:02d0cf66…mobile-price-classificationv2(Python 3.11, matches #56's Dockerfile)sha256:9e0a3a9b…Pushing git tag
v1.0.0later is a no-op for these images:build-images.yamldetects existing release artifacts and preserves them. Future releases should use the next tag.Validation
prokube/releases/<image>:v1.0.0digests match their sourcesprokube-internalorprokube/developmentdefaults remain for these imagesactionlint, YAML parse of changed manifests,py_compile,git diff --check, pre-commit