From a3f160bd405a6814dbe64e8a3dfdeb044b4d0173 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Mon, 22 Jun 2026 13:49:06 +0200 Subject: [PATCH] ci: do not publish a kata-monitor job-dispatcher manifest MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The kata-monitor image has no job-dispatcher sidecar, so opt out of the kata-deploy-specific dispatcher manifest derivation in the payload-after-push workflow by setting KATA_DEPLOY_PUBLISH_JOB_DISPATCHER=false, mirroring the same fix already applied to the release workflows. Signed-off-by: Fabiano Fidêncio --- .github/workflows/payload-after-push.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/payload-after-push.yaml b/.github/workflows/payload-after-push.yaml index b09ec5b778..71ac060e3e 100644 --- a/.github/workflows/payload-after-push.yaml +++ b/.github/workflows/payload-after-push.yaml @@ -267,10 +267,13 @@ jobs: - name: Push multi-arch monitor manifest run: | + # kata-monitor has no job-dispatcher sidecar image, so opt out of the + # kata-deploy-specific dispatcher manifest derivation. ./tools/packaging/release/release.sh publish-multiarch-manifest env: KATA_DEPLOY_IMAGE_TAGS: "kata-monitor-latest" KATA_DEPLOY_REGISTRIES: "quay.io/kata-containers/kata-monitor-ci ghcr.io/${{ github.repository_owner }}/kata-monitor-ci" + KATA_DEPLOY_PUBLISH_JOB_DISPATCHER: "false" upload-helm-chart-tarball: name: upload-helm-chart-tarball