mirror of https://github.com/kata-containers/kata-containers.git synced 2026-07-01 06:28:11 +00:00

Files

Fabiano Fidêncio 5959549645 release: do not publish a kata-monitor-job-dispatcher manifest

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.

Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
Assisted-by: Cursor <cursoragent@cursor.com>

2026-06-15 16:29:29 +02:00

generate_vendor.sh

generate_vendor: Fix heavily broken logic

2026-06-12 10:06:53 +02:00

README.md

releases: Adjust documentation to the new workflow

2024-03-18 12:57:02 +01:00

release.sh

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

2026-06-15 16:29:29 +02:00

README.md

Release information

Introduction

This directory contains information of the process and tools used for creating Kata Containers releases.

Create a Kata Containers release

See the release documentation.

Release tools

`release.sh`

This script is used by GitHub actions in the release file from the kata-containers/kata-containers repository to handle the various steps of the release process.

`generate_vendor.sh`

This script is used by release.sh to generate a tarball with all the cargo vendored code.