chore: bring images up to date #63
Open
casibbald wants to merge 1 commit intoliquidmetal-dev:mainfrom
Open
Conversation
…rnel/CH/CAPMVM naming, liquidmetal-dev)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR brings image naming, workflows, and references in line with the current Liquid Metal setup: registry detection for forks, ARM (experimental) workflows, explicit architecture suffixes on image names, and the move from
weaveworks-liquidmetaltoliquidmetal-dev.Successful builds can be found here:
1. Registry detection (fork-friendly)
REGISTRY=ghcr.io/${{ vars.REGISTRY_OWNER || github.repository_owner }}microscaler/image-builder) publish toghcr.io/microscaler/..., and upstream toghcr.io/liquidmetal-dev/....REGISTRY_OWNERoverrides the owner (e.g. for a different org).kernel-images.yml,kernel-images-manual.yml,capmvm-kubernetes-manual.yml.2. Kernel workflows and images
workflow_dispatchadded to Build and release kernel images for manual runs.firecracker-kernel-amd64,firecracker-kernel-bin-amd64,firecracker-kernel-modules-amd64;cloudhypervisor-kernel-amd64,cloudhypervisor-kernel-bin-amd64,cloudhypervisor-kernel-modules-amd64.firecracker-kernel-arm64,firecracker-kernel-bin-arm64,firecracker-kernel-modules-arm64.git://tohttps://for CI..github/workflows/kernel-images-arm.yml(push onexperimental/arm/kernel/**, manual dispatch, QEMU + Buildx forlinux/arm64).3. CAPMVM workflows and images
capmvm-k8s-ubuntu-{20.04|22.04|24.04}-amd64capmvm-k8s-ubuntu-{20.04|22.04|24.04}-arm64.github/workflows/capmvm-kubernetes-arm-manual.yml(manual dispatch, same inputs as x86: k8s version, containerd, Ubuntu version).-1.1, and OS_VERSION for Ubuntu choice.4. References: weaveworks-liquidmetal → liquidmetal-dev
weaveworks-liquidmetaltoliquidmetal-dev(default REGISTRY, README examples, and links to flintlock, cluster-api-provider-microvm, site, microvm-action-runner).REGISTRYis nowghcr.io/liquidmetal-devwhere applicable.Files changed (22)
kernel-images.yml,kernel-images-manual.yml, newkernel-images-arm.yml,capmvm-kubernetes-manual.yml, newcapmvm-kubernetes-arm-manual.yml.