Summary
The krm-functions-catalog's VERSIONING.md documents support for floating image tags (vX, vX.Y) that should
automatically track the latest patch/minor release. In practice, these tags have never been updated after their initial creation and are stale across all 18 released function images. Additionally, a latest tag exists on 21 images despite the document explicitly stating it is not supported.
This issue proposes deciding whether to fix or remove these tags, and updating VERSIONING.md accordingly.
Current State
Floating minor tags (vX.Y)
Every function image has a floating minor tag that does NOT point to the latest patch release
Floating major tags (v0)
All 18 released function images have a v0 tag that does not point to their latest release.
latest tag exists but documented as unsupported
VERSIONING.md states: "We do NOT officially support the latest tag". However, latest exists on 21 images (18 released functions + annotate-apply-time-mutations, generate-kpt-pkg-docs, no-op, sleep). All are stale.
Questions
-
Should we fix the release CI to maintain floating tags and latest with proper versions, or remove support for them entirely (from both docs and images)?
- Fixing requires CI/CD pipeline changes and retroactively updating all 18 images
- Removing is simpler and reflects what has always been the actual state
- A stale
latest pointing to an old build(Not all) is arguably worse than no latest at all
-
Should a common VERSIONING.md be maintained in the governance repo and referenced across repos, or should each repo own its own versioning doc?
- Currently only the catalog, has a VERSIONING.md (and it's out of date) - It's added now for Kpt.
- The SDK (at v1.0.4) ) has no versioning docs
- A shared doc would ensure consistency but may not capture repo-specific concerns (e.g. container images for catalog, Go modules for SDK, CLI binaries for kpt)
Summary
The
krm-functions-catalog'sVERSIONING.md documents support for floating image tags (vX,vX.Y) that shouldautomatically track the latest patch/minor release. In practice, these tags have never been updated after their initial creation and are stale across all 18 released function images. Additionally, a
latesttag exists on 21 images despite the document explicitly stating it is not supported.This issue proposes deciding whether to fix or remove these tags, and updating VERSIONING.md accordingly.
Current State
Floating minor tags (
vX.Y)Every function image has a floating minor tag that does NOT point to the latest patch release
Floating major tags (
v0)All 18 released function images have a
v0tag that does not point to their latest release.latesttag exists but documented as unsupportedVERSIONING.md states: "We do NOT officially support the
latesttag". However,latestexists on 21 images (18 released functions +annotate-apply-time-mutations,generate-kpt-pkg-docs,no-op,sleep). All are stale.Questions
Should we fix the release CI to maintain floating tags and
latestwith proper versions, or remove support for them entirely (from both docs and images)?latestpointing to an old build(Not all) is arguably worse than nolatestat allShould a common VERSIONING.md be maintained in the governance repo and referenced across repos, or should each repo own its own versioning doc?