76c18aa345
Since we always build musl kata-agent, there is no need to build it inside a musl container. We can just build on the host and then copy the binary to the target rootfs. There are still a lot to clean up and it should be made so for ALL target distros instead of just alpine. But this is at least working for alpine first. Signed-off-by: Peng Tao <bergwolf@hyper.sh>
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
update-repository-version.sh
This script creates a GitHub pull request (a.k.a PR) to change the version in all the Kata repositories.
For more information on using the script, run the following:
$ ./update-repository-version.sh -h
Update Kata projects to a new version
To update project version for Kata Containers, use the following:
$ make bump-kata-version NEW_VERSION=<new-version>
The makefile target bump-kata-version creates a GitHub pull request in the
kata-containers repository. The pull request is tested by the Kata CI to ensure the
entire project is working prior to the release. Next, the PR is approved and
merged by Kata Containers members.
tag_repos.sh
After Kata Containers repository is updated with a new version, it needs to be tagged.
The tag_repos.sh script is used to create tags for the Kata Containers repository.
The script creates an annotated tag for the new release version for the
following repositories:
- kata-containers