Repository navigation
RunR 0.7.1
RunR is an open-source, self-hosted serverless platform on Kubernetes and Knative: functions, containers, sandboxes, WebAssembly and durable workflows, with an API, a web console, the runr CLI, SDKs, a Terraform provider and a GitHub Action. You install it on infrastructure you operate, connected or air-gapped. It is developed by BRF Teknoloji and released under the MIT License.
0.7.1 gives the scheduler the memory its overlapping runs need. Since 0.7.0 the run at the top of the hour can take longer than a minute and overlap the next minute's run; schedule:work, each schedule:run and every artisan command they start hold about 70 MB each, so runr-scheduler went past its 256Mi limit and was OOMKilled several times a day. The chart's default scheduler.resources is now requests 50m / 160Mi and limits 256m / 512Mi (docs/helm-values.md). RunR's dependency bots now report in one weekly summary issue instead of an issue per finding (docs/development.md).
Upgrading from 0.7.0: no migration, no new value, the images of 0.7.0 built again at 0.7.1. With --reuse-values, set the scheduler's two memory values in the upgrade: --reuse-values keeps the old chart's defaults.
Install
- Kubernetes (Helm): the chart comes from BRF's public Helm repository, without credentials:
See the README and docs/install.md;
helm repo add brf-tech https://helm.brf.sh helm upgrade --install runr brf-tech/runr --namespace runr --create-namespace --set domain=runr.example.com
helm show values brf-tech/runrlists every value. A pinned install adds--version 0.7.1; the API and UI images, the region agent and the event gateway follow the chart version. - Single host (Docker Compose, also air-gapped): compose/README.md, from a checkout of the release tag (
git clone -b v0.7.1 https://github.com/BRF-Tech/runr.git). - CLI:
curl -fsSL https://runr.sh/install.sh | shon Linux and macOS. The archives of every platform are at runr.sh/dl (https://runr.sh/dl/cli/v0.7.1/) and attached below; check them againstchecksums.txt(docs/cli.md#install). - Terraform / OpenTofu:
source = "brf-tech/runr",version = "~> 0.6", from the Terraform Registry;terraform initchecks the archive againstSHA256SUMS, signed with the RunR release key (key ID2588846B241BC095). runr.sh serves the same archives underrunr.sh/brf-tech/runr, for OpenTofu and for configurations that use that address (docs/terraform.md#install). - GitHub Action:
uses: brf-tech/runr/actions/deploy@v0.7.1; it downloads the CLI from runr.sh (docs/github-action.md). - Images: every image is published under
ghcr.io/brf-tech/runrby release-images.yml, for linux/amd64 and linux/arm64, and pulls anonymously.
The documentation is at runr.sh/docs and in the documentation index here.
Upgrading from 0.7.0
Upgrade in place with helm upgrade of the running release; never uninstall and install again, and back up the database first (Procedure in docs/upgrade.md). The images keep their names (0.7.0 → 0.7.1).
helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.7.1 -n runr --reuse-values \
--set scheduler.resources.requests.memory=160Mi --set scheduler.resources.limits.memory=512Mi- The scheduler's new default has to reach the release.
--reuse-valuesrenders with the defaults of the chart the release runs, so without the two--setvalues the scheduler stays at64Mi/256Mi.--reset-then-reuse-valuesinstead keeps your values and takes every default of 0.7.1. A release that setsscheduler.resourcesitself keeps its own values: give it at least512Miof memory. The scheduler pod is replaced once. - Nothing else an installation runs changes. The API, the console, the region agent and the event gateway are those of 0.7.0 at the version 0.7.1. As in every release, after
helm upgradereturned, the Jobrunr-region-reconcile-<revision>moves the regions' agents, queue consumers and topic publishers toghcr.io/brf-tech/runr/agent:0.7.1andqueue-consumer:0.7.1; each rolls once. A region that pulls through a mirror of its own needs these two images there before the upgrade (Order of operations). - Back to 0.7.0: a
helm rollback; nothing runs on the database. The scheduler goes back to64Mi/256Mi(Back to 0.7.0). - CLI and Terraform provider 0.7.1: the code of 0.7.0's; the provider's resources and data sources are the ones of 0.6.10.
From 0.6.13, upgrade straight to 0.7.1 and read 0.6.13 → 0.7.0 first: 0.7.0 adds two migrations (knative_regions.kubernetes_version, and the existing wasm-rust and wasm-js projects without a runtime version pinned to 4.1), runs Helm 4 for the region releases (Helm 4) and the kubectl of each region's Kubernetes minor (kubectl per region), and moves gateway-auth to 1.1.0 and the Spin shim to v0.27.2-runr.1; a rollback to 0.6.13 needs the projects moved to WebAssembly 4.2 set back to 4.1 first (Back to 0.6.13). From 0.6.10 to 0.6.12, upgrade straight to 0.7.1 and read 0.6.13 → 0.7.0 as well: 0.6.11 and 0.6.13 only moved Go modules of a region image (the queue consumer's and image-upload's, the security update of github.com/klauspost/compress, GO-2026-6865, among them) and 0.6.12 fixed RunR's release tooling; none of them needs a step (0.6.12 → 0.6.13, 0.6.11 → 0.6.12, 0.6.10 → 0.6.11). From 0.6.0 to 0.6.9, upgrade straight to 0.7.1 and read the security release 0.6.9 → 0.6.10 first: after the upgrade, check the routes of every project in access mode allowlist (After the upgrade). From 0.6.8, also read 0.6.8 → 0.6.9: 0.6.9 adds a column (projects.capacity_released_at, and in every tenant schema), a stopped project gives its capacity back in a pay-as-you-go region and is admitted again on resume, and a region with many stopped projects can raise the capacity alarm right after the upgrade. From 0.6.7, also read 0.6.7 → 0.6.8: 0.6.8 adds runtime sources and RunR's signed runtime catalog, which the API reads from ghcr.io (runtimeCatalog.offline: true keeps the bundled one), gives single-tenant Owners platform.manage, moves the region Traefik to chart 42.3.1, and a marketplace that merges the package's default values into an upgrade can bring ingress.tls.mode: letsencrypt to a release that never set it (The console certificate warning). From 0.6.6, also read 0.6.6 → 0.6.7: 0.6.7 changes how sandbox commands travel on Kata and gVisor (a command on gVisor takes about 100 ms more), input that arrives short fails, and a custom sandbox image needs cat and mkfifo. From 0.6.5, also read 0.6.5 → 0.6.6: 0.6.6 re-runs kata-deploy with Kata Containers 4.3.1, which stops the running Kata pods of every region with Kata, the region Traefik moves to chart 42.3.0 and deletes request headers with _ or . in their names, and Reverb refuses client events. From 0.6.4, also read 0.6.4 → 0.6.5: 0.6.5 adds the notification_user_states migration, the Helm value notifications.retentionDays, and its daily task deletes notifications older than 90 days. From 0.6.3, also read 0.6.3 → 0.6.4: 0.6.4 adds the captcha_settings migration and the Helm values captcha.*, and its first upgrade rolls the pods once. From 0.6.2, also read 0.6.2 → 0.6.3; from 0.6.1, also 0.6.1 → 0.6.2. From 0.6.0, also read 0.6.0 → 0.6.1 first: before a rollback to 0.6.0, let the running deploys finish (Rolling back to 0.6.0). From 0.5.10, read 0.5.10 → 0.6.0 in docs/upgrade.md first — in particular what to decide before the upgrade — and the notes of 0.6.0 to 0.6.9 in CHANGELOG.md; everything said there applies. From 0.5.9 or earlier, read the notes of the releases in between as well; from 0.5.8 or earlier, add --set api.image.tag= --set ui.image.tag= to that upgrade once (step 3 of the Procedure).
Changes in 0.7.1 (2026-11-14)
Upgrade notes
- Upgrading from 0.7.0 needs no migration and no new value, but the scheduler's new default has
to reach the release. The images of 0.7.0 are built again at 0.7.1, and the scheduler pod is
replaced once.helm upgrade --reuse-valuesrenders with the defaults of the chart the release
runs, so it would keep the scheduler at64Mi/256Mi: add
--set scheduler.resources.requests.memory=160Mi --set scheduler.resources.limits.memory=512Mi,
or upgrade with--reset-then-reuse-valuesinstead
(0.7.0 → 0.7.1 in upgrade.md). - Back to 0.7.0 is a
helm rollback; nothing runs on the database.
Changed
- The dependency bots report in one weekly summary. Instead of an issue per finding, the daily
release check and the dependency test bot keep one issue per week,deps: week <ISO week>, with
one row per dependency and its state (new,testing,green,green → shipped in vX.Y.Z,
red,needs attention,held (<reason>),closed); a quiet week opens none, and the rows
still open carry over to the next one. A security finding is a row flaggedsecurity: <advisory>
and is still tested the same day. A separate issue only where a person has to do something: a
bump that went red, a test run that needs a person, and one issue per group for its major
versions (closed when its list is empty); a major held with a written reason is aheldrow
instead. The findings filed as issues of their own before are folded into the first summary. See
docs/development.md.
Fixed
- The scheduler no longer runs out of memory. Since 0.7.0 the run at the top of the hour can
take longer than a minute, and then it overlaps the next minute's run.schedule:work, each
schedule:runand every artisan command they start hold about 70 MB each. With those overlaps
runr-schedulerwent past its 256Mi limit and was OOMKilled several times a day: 5 times in its
first 31 hours on both test regions. The default is now requests50m/160Miand limits
256m/512Mi(scheduler.resources). A release that setsscheduler.resourcesitself keeps
its own values.