Skip to content

RunR 0.7.5

Latest

Choose a tag to compare

@brkfun brkfun released this 15 Nov 12:38
v0.7.5

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.5 moves the region Traefik to v3.7.18, which fixes five upstream security advisories, and kube-prometheus-stack to 93.3.0; it builds the region images on alpine 3.22, and the runr CLI and the Terraform provider, the first since 0.7.3, with newer Go modules. RunR's dependency test bot now attempts every update.

  • Traefik v3.7.18 (chart 42.3.1 → 42.4.0, its image from the reqs mirror, ghcr.io/brf-tech/runr/reqs/traefik:v3.7.18): region:reconcile moves every region's Traefik by itself, one pod at a time. It fixes four high advisories and a medium one: path-parameter dot-segments that bypassed path-based authorization (GHSA-cp28-5662-543f), ForwardAuth with NTLM through Proxy-Authorization (GHSA-p956-6gvv-mxqp), memory exhaustion by the Compress middleware (GHSA-x5pf-cqh3-2gv8), the Ingress-NGINX provider's client certificates (GHSA-ccgh-9g52-6vwg) and BasicAuth passwords of any length (GHSA-rr42-h8r2-f28g). With sanitizePath, which RunR's entry points enable, a request for /a/..;x/b now reaches the function as /b (Traefik's migration notes).
  • kube-prometheus-stack 93.3.0 (a new major version; Prometheus Operator v0.94.2 → v0.95.2): regions set up from now on run it; an installed region moves when you run php artisan cluster:patch-observability [REGION-ID] (the operator, Prometheus and node-exporter restart once). No CRD step: the new CRDs only add fields.
  • Alpine 3.22: the region agent and the queue consumer 0.7.5 and the supply-chain image 1.1.2 (from 1.1.1) build on it. The Spin shim stays containerd-shim-spin:v0.27.2-runr.1 on alpine 3.21: built on 3.22 it failed the WebAssembly suite, and its move waits as next update required (#80).
  • CLI 0.7.5: github.com/spf13/cobra v1.8.1 → v1.10.2, github.com/spf13/pflag v1.0.5 → v1.1.0, golang.org/x/sys v0.48.0 → v0.50.0, golang.org/x/term v0.32.0 → v0.48.0. Its commands and flags are those of 0.7.3; its help writes a boolean flag as --debug[=true|false], and runr completion bash / powershell print cobra 1.10's scripts.
  • Terraform provider 0.7.5: github.com/ProtonMail/go-crypto v1.4.1 → v1.5.2, github.com/hashicorp/go-plugin v1.7.0 → v1.8.0, github.com/hashicorp/hc-install v0.9.4 → v0.10.0, golang.org/x/sys v0.48.0 → v0.50.0, built against the CLI module v0.7.5. Its resources and data sources are those of 0.6.10.
  • The dependency test bot attempts every update (docs/development.md): a new major, a release outside a manifest's constraint or exact pin, and a chart's new major are tested on its weekly run like any other version. What it cannot move mechanically, or what fails its suites, gets the label next update required with the failing suite and is tried again every week until it passes; holds are never attempted and are listed with their reasons in the weekly summary.
  • CI tool pins: RunR's workflows run helm v4.3.2 (the release workflow packages the chart with it), terraform 1.17.2 and govulncheck v1.9.0.
  • Examples and the development stack: the PyTorch weights example takes transformers 5.23.0; the Sentry tunnel of the root docker-compose.yml (proxy/, no release image) moves github.com/redis/go-redis/v9 to v9.23.0.

Upgrading from 0.7.4 needs no migration and no new value. The region Traefik moves by itself; kube-prometheus-stack moves when you run cluster:patch-observability.

Install

  • Kubernetes (Helm): the chart comes from BRF's public Helm repository, without credentials:
    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
    See the README and docs/install.md; helm show values brf-tech/runr lists every value. A pinned install adds --version 0.7.5; 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.5 https://github.com/BRF-Tech/runr.git).
  • CLI: curl -fsSL https://runr.sh/install.sh | sh on Linux and macOS. The archives of every platform are at runr.sh/dl (https://runr.sh/dl/cli/v0.7.5/) and attached below; check them against checksums.txt (docs/cli.md#install).
  • Terraform / OpenTofu: source = "brf-tech/runr", version = "~> 0.6", from the Terraform Registry; terraform init checks the archive against SHA256SUMS, signed with the RunR release key (key ID 2588846B241BC095). runr.sh serves the same archives under runr.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.5; it downloads the CLI from runr.sh (docs/github-action.md).
  • Images: every image is published under ghcr.io/brf-tech/runr by 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.4

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 and nothing has to be set (0.7.4 → 0.7.5).

helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.7.5 -n runr --reuse-values
  • What moves in a region by itself. After helm upgrade returned, the Job runr-region-reconcile-<revision> moves the regions' agents, queue consumers and topic publishers to ghcr.io/brf-tech/runr/agent:0.7.5 and queue-consumer:0.7.5, and the region Traefik to chart 42.4.0 (v3.7.18); each rolls once, Traefik one pod at a time. With knative.traefikImage set, the region keeps that image on the new chart. A region that pulls through a mirror of its own needs agent:0.7.5, queue-consumer:0.7.5, supply-chain:1.1.2 and ghcr.io/brf-tech/runr/reqs/traefik:v3.7.18 there before the upgrade (Order of operations).
  • kube-prometheus-stack 93.3.0 waits for you: php artisan cluster:patch-observability [REGION-ID] moves an installed region when it suits it. RunR needs no CRD step. If you create Prometheus Operator objects of your own with fields that v0.95.2 adds, apply the chart's CRDs on the region's cluster first (--force-conflicts: Helm created the installed CRDs and owns their fields):
    helm show crds kube-prometheus-stack --repo https://prometheus-community.github.io/helm-charts \
      --version 93.3.0 | kubectl apply --server-side --force-conflicts -f -
  • Back to 0.7.4: a helm rollback; nothing runs on the database. The region Traefik stays on chart 42.4.0 (0.7.4 moves no Traefik to an older chart), and a region moved to kube-prometheus-stack 93.3.0 stays on it (Back to 0.7.4).
  • CLI and Terraform provider 0.7.5: the code of 0.7.3's with the Go modules above (0.7.4, a dependency release, shipped neither). curl -fsSL https://runr.sh/install.sh | sh installs the CLI 0.7.5; a configuration with version = "~> 0.6" takes the provider 0.7.5 on its next terraform init -upgrade.

From 0.7.3, upgrade straight to 0.7.5: 0.7.4, a dependency release of 0.7.3, needs no step of its own (0.7.3 → 0.7.4); it moved the API's Composer packages, gateway-auth and the supply-chain image to 1.1.1 and the Zot chart of new registries to 0.1.134 (an installed Zot keeps its chart until php artisan registry:upgrade-zot <region>). From 0.7.1 or 0.7.2, upgrade straight to 0.7.5 as well: 0.7.3 changed nothing an installation runs and 0.7.2 only moved Go modules of the region agent (0.7.2 → 0.7.3, 0.7.1 → 0.7.2). From 0.7.0, upgrade straight to 0.7.5 and read 0.7.0 → 0.7.1 first: --reuse-values keeps the scheduler at the 64Mi / 256Mi of the old chart, so add --set scheduler.resources.requests.memory=160Mi --set scheduler.resources.limits.memory=512Mi to that upgrade (or upgrade with --reset-then-reuse-values); the same holds for every release before 0.7.1 below. From 0.6.13, upgrade straight to 0.7.5 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.5 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.5 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.5 (2026-11-15)

Upgrade notes

  • No migration, no new Helm value. The region Job moves the region agent and the event
    gateway (agent, queue-consumer) to 0.7.5 as in every release; both images and the
    supply-chain image 1.1.2 (from 1.1.1) build on alpine 3.22. A region that pulls through a mirror
    of its own needs agent:0.7.5, queue-consumer:0.7.5 and supply-chain:1.1.2 there first
    (0.7.4 → 0.7.5 in upgrade.md).
  • kube-prometheus-stack 93.3.0 does not reach an installed region by itself:
    php artisan cluster:patch-observability [REGION-ID] moves it when it suits the region (the
    Prometheus Operator, Prometheus and node-exporter restart once). No CRD step is needed.
  • Your own monitoring objects: RunR needs no CRD step. If you create Prometheus Operator
    objects of your own (ServiceMonitors, PrometheusRules, AlertmanagerConfigs) with fields that
    v0.95.2 adds, apply the chart's CRDs on the region's cluster first; --force-conflicts is needed
    because Helm created the installed CRDs and owns their fields:
    helm show crds kube-prometheus-stack --repo https://prometheus-community.github.io/helm-charts --version 93.3.0 | kubectl apply --server-side --force-conflicts -f -.
  • The region Traefik moves to v3.7.18 by itself (region:reconcile, step traefik-chart). A
    region whose nodes pull through a mirror of their own needs
    ghcr.io/brf-tech/runr/reqs/traefik:v3.7.18 there first; with knative.traefikImage set, the
    region keeps that image on the new chart.
  • Traefik v3.7.18 fixes five upstream advisories (four high, among them a bypass of
    path-based authorization through path-parameter dot-segments, GHSA-cp28-5662-543f, on entry
    points with sanitizePath, which RunR's regions enable) and changes what they touched: a request
    for /a/..;x/b reaches the function as /b, and BasicAuth refuses passwords over 1024 bytes
    (Traefik's migration notes).
  • CLI and Terraform provider 0.7.5 are the first since 0.7.3 (0.7.4, a dependency release,
    shipped neither): the code of 0.7.3, built with the CLI's and the provider's Go modules below.
    Their commands, flags, resources and data sources stay those of 0.7.3; the CLI's help writes a
    boolean flag as --debug[=true|false].
  • Back to 0.7.4 is a helm rollback; nothing runs on the database. The region Traefik stays
    on chart 42.4.0 (0.7.4's region:reconcile moves no Traefik to an older chart and warns that it
    stays), and a region moved to kube-prometheus-stack 93.3.0 stays on it.

Changed

  • CLI Go modules moved (minor and patch updates, nothing a release image ships):
    github.com/spf13/cobra v1.8.1 → v1.10.2, github.com/spf13/pflag v1.0.5 → v1.1.0, golang.org/x/sys
    v0.48.0 → v0.50.0, golang.org/x/term v0.32.0 → v0.48.0.
  • Sentry tunnel Go modules moved (minor and patch updates, nothing a release image ships):
    github.com/cespare/xxhash/v2 v2.2.0 → v2.3.0, github.com/dgryski/go-rendezvous
    v0.0.0-20200823014737-9f7001d12a5f → none, github.com/redis/go-redis/v9 v9.7.3 → v9.23.0,
    go.uber.org/atomic none → v1.12.0, golang.org/x/sys none → v0.48.0.
  • Terraform provider Go modules moved (minor and patch updates, nothing a release image ships):
    github.com/ProtonMail/go-crypto v1.4.1 → v1.5.2, github.com/hashicorp/go-plugin v1.7.0 → v1.8.0,
    github.com/hashicorp/hc-install v0.9.4 → v0.10.0, golang.org/x/sys v0.48.0 → v0.50.0.
  • CI tool pins moved (minor and patch updates, nothing a release image ships): helm v4.3.1 →
    v4.3.2, terraform 1.13.3 → 1.17.2, govulncheck v1.1.4 → v1.9.0.
  • The dependency test bot attempts every update by itself. A new major, a release outside a
    manifest's constraint or exact pin (the constraint moves mechanically: ^7 → ^8, ==X → ==Y,
    a Go module's new major path with its imports, an Actions pin's new major) and a chart's new major
    are tested on the weekly run like any other version; a Traefik chart with a new app version gets
    its image copied into the reqs mirror (ghcr.io/brf-tech/runr/reqs/traefik) by the job Reqs
    mirror before its suites. What the bot cannot move mechanically, or what fails its suites, gets
    the label next update required (instead of needs attention), with the failing suite and its
    log, and a line in the weekly summary's own section Next update required; every weekly run tries
    it again, and once it passes it ships, loses the label and closes. Holds (ci/deps/holds.txt)
    are never attempted and are listed there with their reasons. The major versions issues are closed
    with a pointer to the summary.
  • A release of the bot says when a major moved: its upgrade notes, docs/upgrade.md and the
    GitHub release say A new major version moves: …, and the dependency's line says what an
    installed region does (the step that moves its chart, and for a chart whose CRDs changed the
    command that applies them). A dry run copies nothing into the reqs mirror: its suites take the
    upstream image under the mirror's name.
  • Dockerfile base images moved (minor and patch updates): ghcr.io/brf-tech/runr/reqs/alpine 3.21
    → 3.22, ghcr.io/brf-tech/runr/reqs/alpine 3.20 → 3.22, supply-chain image 1.1.1 → 1.1.2 (its own
    version: release-images.yml builds it). The images build on the new bases; the Spin shim's stays
    on 3.21 (#80).
  • Hugging Face weights example packages moved (outside the constraint ==5.22.2, an exact pin
    moved by hand; nothing a release image ships): transformers 5.22.2 → 5.23.0 in
    examples/ai/hf-python/weights. 5.23.0 changes nothing the example uses (AutoTokenizer and
    AutoModel loading a mounted snapshot offline); its handler answers on exec-pytorch's torch
    2.14.1 (CPU).
  • Region Traefik chart 42.4.0 (from 42.3.1; Traefik v3.7.17 → v3.7.18). New regions install it;
    region:reconcile moves the Traefik of an existing region to it (step traefik-chart), one pod
    at a time. Its image comes from the reqs mirror (ghcr.io/brf-tech/runr/reqs/traefik:v3.7.18);
    with knative.traefikImage set, the region keeps that image. Only the Traefik Hub CRDs change (an
    optional caSecretName in APIAuth and APIPortalAuth), which RunR does not use: an installed
    region needs no CRD step.
  • kube-prometheus-stack 93.3.0 (from 92.22.0, a new major version; Prometheus Operator v0.94.2 →
    v0.95.2). Regions installed from now on run it; an installed region keeps its chart until php artisan cluster:patch-observability, a change back to RunR's own monitoring or a new Serving
    install moves it. Prometheus (v3.16.0), kube-state-metrics and node-exporter keep their versions;
    the operator's ClusterRole follows upstream's of v0.95 (alertmanagerconfigs/status added,
    delete on pods gone). On that move the operator, Prometheus (its config reloader) and
    node-exporter restart once. The operator's new CRDs only add optional fields and validations of
    fields RunR does not set: an installed region keeps its CRDs (Helm does not upgrade them) and
    needs no CRD step.