use a GitHub action to push to GitHub Container Registry #444
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.
Maintaining multiple Dockerfiles for different architectures became tedious. Furthermore, the pipeline frequently ran into rate-limiting issues on quay.io.
This PR switches the container image build pipeline to GitHub Actions and instead builds a multi-arch image (image index) using qemu to support the previously available architectures.
This changes the "official" image location from quay.io to ghcr.io as well as the semantics of the tags of the produced images:
ghcr.io/linki/chaoskube:master
will be the very latest (unstable) version from the master branchghcr.io/linki/chaoskube:v0.23.3
will be for versionv0.23.3
ghcr.io/linki/chaoskube:v0.23
will be for the latest patch version within thev0.23.x
groupghcr.io/linki/chaoskube:latest
will point to the latest released version (so it might be behind master and is basically what was requested here: Lifecycle with release tags #128 (comment))All images will be multi-arch for
linux/amd64
,linux/arm64
,linux/arm/v6
, andlinux/ppc64le
(the previously available images on quay.io) so there won't be any-arm64
etc. suffixes to the tags anymore.