ci: bake image version into OCI kustomize bundle#8
Merged
Conversation
Point publish-kustomize-bundle's image-overlays at config/base/manager — that's where the images: block lives, so the action's `kustomize edit set image` call lands on the right kustomization and the published OCI bundle now ships with the resolved image tag baked in. Realign all manifest image references from ghcr.io/datum-cloud/inventory to ghcr.io/milo-os/inventory so the name matches the actual registry path used by publish-docker (registry-organization: milo-os) and the image-name input on the kustomize-bundle workflow. Fixes #7. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
scotwells
approved these changes
May 27, 2026
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
image-overlaysin.github/workflows/publish.yamlfromconfig/basetoconfig/base/manager— that's where theimages:block actually lives, so the upstreampublish-kustomize-bundleaction'skustomize edit set imagecall now lands on the right kustomization and the resolved tag is baked into the published OCI bundle.ghcr.io/datum-cloud/inventory→ghcr.io/milo-os/inventory(manager kustomization, deployment manifest, dev overlay, Taskfile var). The published image actually ships toghcr.io/milo-os/inventory(perpublish-docker'sregistry-organization: milo-os+image-name: inventory), andimage-nameon the kustomize-bundle workflow is already set to that path — so the manifests must agree, otherwisekustomize edit set imageis a no-op against a non-matching name.Mirrors the billing service pattern referenced in the issue.
Closes #7.
Test plan
Publish Inventoryworkflow;publish-kustomize-bundlesstep logsSetting image ghcr.io/milo-os/inventory:<tag> in .../config/base/managerand shows the modified kustomization.yaml with the resolved tag (notlatest).flux pull artifact oci://ghcr.io/milo-os/inventory-kustomize:<tag>) and confirmconfig/base/manager/kustomization.yamlimages[].newTagmatches the docker tag.task dev:setupstill stands up the controller locally against the new image name.🤖 Generated with Claude Code