Repository navigation
Conversation
urunc-deploy installs urunc and every hypervisor it drives, except hluk, the monitor of Hyperlight guests, which had to be put on the PATH of each node by hand. A build stage downloads the hluk release for the build architecture, checks it against the sums the release publishes and places it next to the other hypervisors. hluk embeds the kernel it boots and its Linux releases are static binaries, so that one file is all a node needs. The version is a build argument with the release as its default, and the Dockerfile notes what it moves together with. hluk joins the default HYPERVISORS list of the DaemonSet and is copied to /opt/urunc/bin like the rest; uninstall already removes that directory. The shipped configuration points the hyperlight-unikraft monitor at that path, which urunc takes over a PATH lookup. The path is only kept when urunc-deploy installed hluk: a deployment whose HYPERVISORS leaves it out keeps resolving a hand-installed hluk from the PATH as it does today, and the URUNC_MONITORS_HYPERLIGHT_UNIKRAFT_PATH variable sets it either way. Signed-off-by: danbugs <danilochiarlone@gmail.com>
The Kubernetes tutorial lists hluk among what urunc-deploy installs and documents the HYPERVISORS variable of the DaemonSet, and the hypervisor support page says that on Kubernetes there is nothing to install by hand. Signed-off-by: danbugs <danilochiarlone@gmail.com>
The urunc-deploy test checks for the binary on the node and, on amd64, runs the hello-hyperlight-unikraft image through the installed hluk, which prints its greeting. The step describes the pod before reading its logs, so a failure shows why. Signed-off-by: danbugs <danilochiarlone@gmail.com>
✅ Deploy Preview for urunc ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This branch has not been deployed
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.
Description
urunc-deploy installs urunc and every hypervisor it drives on the nodes of a cluster, except
hluk, the monitor of Hyperlight guests, which had to be put on thePATHof each node by hand. This shipshlukin the urunc-deploy image and installs it with the others, so a cluster runs Hyperlight images as soon as urunc-deploy has rolled out.HLUK_VERSION, defaulting to the release, and the Dockerfile notes what it moves together with:HLUK_VERSIONinvm_test.yml,hyperlight-unikraftinversions.ymland the test image tag.hlukjoins the defaultHYPERVISORSlist of the DaemonSet and is copied to/opt/urunc/bin/hluklike the rest; uninstall already removes that directory. The shippedconfig.tomlpoints thehyperlight-unikraftmonitor at that path, which urunc takes over aPATHlookup. The path is only kept when urunc-deploy installed hluk: a deployment whoseHYPERVISORSleaves it out keeps resolving a hand-installedhlukfrom thePATHas it does today, andURUNC_MONITORS_HYPERLIGHT_UNIKRAFT_PATHsets it either way.HYPERVISORS; the hypervisor-support page says Kubernetes needs no manual install.docker.io/urunc/hello-hyperlight-unikraft:v0.18.0on amd64, which prints its greeting through the installed hluk. That workflow runs nightly and on dispatch against the image built frommain, so the new steps take effect once this is merged.Related issues
Part of #140, following #1135.
How was this tested?
Built the image from this tree and ran the DaemonSet on a kind cluster (kindest/node v1.35.8, containerd 2.3.4). With the default
HYPERVISORS, the node gets hluk 0.18.0 at/opt/urunc/bin/hluk,/etc/urunc/config.tomlcarries its path, and aruntimeClassName: uruncpod ofdocker.io/urunc/hello-hyperlight-unikraft:v0.18.0prints "hello from Python 3.12.15 on Unikraft in a Hyperlight micro-VM, via urunc". With hluk removed fromHYPERVISORS, nothing is installed and the path line is absent, with the comments of the file kept. The installer passesbash -nand shellcheck with no new findings, the workflow passes actionlint and cspell. No Go code changes;make lintreports nothing new andmake test_dockerpasses except the Firecracker FreeBSD case, which asks docker for anio.containerd.urunc-fc.v2runtime mine does not define.LLM usage
Fable 5.1
Checklist
make lint).make test_ctr,make test_nerdctl,make test_docker,make test_crictl).