github/kata-containers
1
0
Fork 2
mirror of https://github.com/kata-containers/kata-containers.git synced 2026-07-12 10:16:48 +00:00
Code Issues Projects Releases Wiki Activity

release: do not publish a kata-monitor-job-dispatcher manifest

Browse Source 
The shared _publish_multiarch_manifest() helper always derived a
"-job-dispatcher" registry from the registries it was given. However, the
dispatcher is a kata-deploy-specific sidecar image, so when the helper
was reused to publish the kata-monitor multi-arch manifest it wrongly
tried to push a non-existent kata-monitor-job-dispatcher image.

Let's gate the dispatcher derivation behind
KATA_DEPLOY_PUBLISH_JOB_DISPATCHER (defaulting to true so the
kata-deploy path is unchanged) and opt out of it when publishing the
kata-monitor manifest.
This commit is contained in:
Fabiano Fidêncio
2026-06-13 13:47:30 +02:00
parent a843844ccb
commit 888ed024f0
2 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.github/workflows/release-kata-images.yaml vendored
View File

@@ -108,6 +108,9 @@ jobs:
TAGS: ${{ needs.resolve-tags.outputs.tags }}
REGISTRIES: ${{ inputs.registries }}
run: |
# kata-monitor has no job-dispatcher sidecar image, so opt out of the
# kata-deploy-specific dispatcher manifest derivation.
KATA_DEPLOY_IMAGE_TAGS="${TAGS}" \
KATA_DEPLOY_REGISTRIES="${REGISTRIES}" \
KATA_DEPLOY_PUBLISH_JOB_DISPATCHER="false" \
./tools/packaging/release/release.sh publish-multiarch-manifest