Skip to content

RunR 0.7.0

Choose a tag to compare

@brkfun brkfun released this 13 Nov 02:53
· 13 commits to main since this release
v0.7.0

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.0 moves RunR to the current major versions of its dependencies. The API runs Helm 4 for the releases it installs on the region clusters and the kubectl of each region's Kubernetes minor (1.31, 1.33, 1.35 or 1.37); every Go module is on Go 1.27.4; the supply-chain image runs Trivy 0.76 and cosign 3; the Spin shim is v0.27.2 (Spin 4.2.6); the console builds with Vite 8 and runs on vue-router 5, Pinia 4, Sentry 11 and xterm.js 6; the API reference is an OpenAPI 3.1 document. wasm-rust and wasm-js get version 4.2 (Spin Rust SDK 8 on WASIp3, esbuild 0.28), the default of new projects, while the existing projects stay on 4.1. A new API key works at once on every gateway-auth pod, and the timed warmer holds on Knative 1.21 and later.

Upgrading from 0.6.13 is a helm upgrade with nothing to set: two migrations (a new column, and the existing wasm-rust and wasm-js projects without a runtime version pinned to 4.1), then the region Job brings the regions' images to 0.7.0's.

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.0; 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.0 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.0/) 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.0; 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.6.13

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). Nothing has to be set (0.6.13 → 0.7.0).

helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.7.0 -n runr --reuse-values
  • Two migrations, in the central schema and in every organization's: knative_regions.kubernetes_version (a new column; additive), and the existing wasm-rust and wasm-js projects without a runtime version are set to 4.1, the version their code was written for, so the new default 4.2 does not move them (WebAssembly). Projects that name a version keep it.
  • The region Job runr-region-reconcile-<revision>, after helm upgrade returned, records each region's Kubernetes version and moves its agent, queue consumers and topic publishers to ghcr.io/brf-tech/runr/agent:0.7.0 and queue-consumer:0.7.0, gateway-auth to 1.1.0, and on a region with WebAssembly the Spin shim to containerd-shim-spin:v0.27.2-runr.1 (the wasm-installer replaces the binary one node at a time, without a container runtime restart). Uploads use image-upload:1.2.0 and the supply-chain Jobs supply-chain:1.1.0. A region that pulls through a mirror of its own needs these images there before the upgrade (Order of operations).
  • Helm 4 in the API: RunR applies the region releases client-side and waits for them as Helm 3 did, so they upgrade as before. If you run Helm 4 yourself, do not pass --server-side=true to the upgrade of an existing release, and --atomic is --rollback-on-failure there (Helm 4).
  • kubectl per region: the console's terminal and the sandbox commands that go through kubectl exec run the kubectl of the region's Kubernetes minor. A SANDBOX_KUBECTL you set still names one binary for every cluster; leave it unset to let RunR pick (Kubernetes version).
  • WebAssembly 4.2: a project moves to 4.2 with its code ported to the new SDK, by PUT /api/projects/{id} {"runtime_version": "4.2"} (docs/wasm.md). RunR's runtime catalog carries 4.2 from this release on; an installation still on 0.6.x keeps wasm-rust and wasm-js as they were and shows them as a problem of the catalog source until it is upgraded.
  • Your own patch feed, if you sign one with cosign 3, needs the flags RunR's supply-chain image uses (Runtime patch feed).
  • The Python SDKs (runr-sandbox, runr-workflows) require Python 3.11 or newer; the Node.js SDK packages still run on Node.js 18. Building the console yourself needs Node.js 22.12 or newer.
  • Back to 0.6.13: a helm rollback. The column and the 4.1 pins stay (0.6.13 does not read the column, and 4.1 is what it runs); set a project you moved to 4.2 back to 4.1 first, since 0.6.13 has no 4.2 (Back to 0.6.13).
  • CLI and Terraform provider 0.7.0: runr runtimes template --runtime-version and runr init --runtime-version fetch the starter of that runtime version; both are built with Go 1.27.4, and the provider's resources and data sources are the ones of 0.6.10. version = "~> 0.6" takes 0.7.0.

From 0.6.10 to 0.6.12, upgrade straight to 0.7.0: 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.0 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.0 (2026-11-13)

Upgrade notes

  • Upgrading from 0.6.13 needs nothing set. Two migrations, central and per organization:
    knative_regions.kubernetes_version (a new column) and the WebAssembly pin below. The region Job
    records each region's Kubernetes version and moves the region agent and the event gateway to
    0.7.0, gateway-auth to 1.1.0 and, on a region with WebAssembly, the Spin shim to v0.27.2-runr.1
    (one node at a time, no container runtime restart); a region that pulls through a mirror of its
    own needs these images there first (0.6.13 → 0.7.0 in upgrade.md).
  • WebAssembly: the migration pins the existing wasm-rust and wasm-js projects without a
    runtime version to 4.1, so the new default 4.2 does not move them to an SDK their code was not
    written for; nothing has to be done (docs/upgrade.md).
  • Helm 4: RunR's region releases stay client-side and upgrade as before. With your own Helm 4,
    do not pass --server-side=true to the upgrade of an existing release
    (Helm 4 in upgrade.md).
  • kubectl: a SANDBOX_KUBECTL set through extraEnv still names one kubectl for every region;
    take it out to let RunR run the kubectl of each region's Kubernetes minor
    (kubectl per region).
  • A patch feed of your own signed with cosign 3 needs
    --use-signing-config=false --new-bundle-format=false --tlog-upload=false
    (docs/security.md).
  • Back to 0.6.13 is a helm rollback; the column and the 4.1 pins stay. Set a project moved to
    4.2 back to 4.1 first: 0.6.13 has no 4.2 (Back to 0.6.13).

Added

  • WebAssembly runtimes 4.2, next to 4.1, the default of new projects. wasm-rust and
    wasm-js have a second version with the next SDK generation: Rust on the Spin Rust SDK 8
    (#[http_service] async fn, wasm32-wasip2, WASIp3), JavaScript bundled with esbuild 0.28. New
    projects get 4.2 unless they pick 4.1 (the runtime picker, runtime_version); the starter code is
    the picked version's. 4.1 is unchanged, and the upgrade pins the existing projects without a
    version to it (see the upgrade notes). Code of one generation does not build on the other: a
    project moves to 4.2 with its code ported, by PUT /projects/{id} {"runtime_version": "4.2"}
    (docs/wasm.md); examples/wasm is 4.2's code. Both
    versions run on the same Spin shim (Spin 4.2.6); the images are
    ghcr.io/brf-tech/runr/exec-wasm-{rust,js}:4.2 of BRF-Tech/runr-runtimes. wasm-go stays on
    4.1 (TinyGo, Spin Go SDK v2): the Spin Go SDK v4 needs WASIp3 support in a Go release.
  • A runtime version can bring its own starter and build files (versions[].template,
    versions[].build.files in the runtime manifest: docs/runtimes.md),
    for an SDK generation side by side with the one before it. GET /runtimes/{id}/template takes
    ?version=, the console's starter preview shows the picked version's, and
    runr runtimes template --runtime-version / runr init --runtime-version fetch it. A project
    moves to another version of its runtime with runtime_version in PUT /projects/{id}.
  • A new API key works at once on every gateway-auth pod. A pod that meets a key or a route it
    does not know asks RunR again before it answers (the on-demand sync) instead of answering 401 (or
    503 route_unknown) until its next fetch, up to SYNC_SECONDS later: a key used right after its
    creation no longer gets 401 from one pod and 200 from another. One such fetch runs at a time per
    pod, at most one every 2 seconds (apiProduct.onDemandSyncSeconds, 0 turns it off), so a
    flood of invalid keys costs RunR little; a revoked key still stops within SYNC_SECONDS
    (docs/api-product.md). It comes with gateway-auth 1.1.0, which a
    region gets from the upgrade's region:reconcile.

Changed

  • The API runs the kubectl of each region's Kubernetes minor. kubectl is supported within one
    minor of the API server it talks to, and RunR accepts clusters from Kubernetes 1.30 on: the API
    image carries kubectl 1.31.14, 1.33.13, 1.35.10 and 1.37.2 (/usr/local/lib/runr/kubectl/<minor>/;
    kubectl on the PATH is 1.37), and the console's terminal and the sandbox commands that go
    through kubectl exec run the one of the region's minor, else the one below it, else the one
    above. A region records its cluster's version (knative_regions.kubernetes_version, a new
    column) when its kubeconfig is checked and when it moves to another cluster; the region:reconcile
    of the upgrade records it for the existing regions and every run reads it again. A cluster newer
    than 1.38 takes kubectl 1.37 and the API logs a warning once; SANDBOX_KUBECTL (now unset by
    default) still names one binary for every cluster
    (docs/regions.md). The chart's bootstrap Job reads and
    patches runr-admin with runr-kubectl, which picks the same way by the install cluster's
    version (GET /version). The dependency bot moves each kubectl within its minor and reports a
    Kubernetes minor newer than the newest one's.
  • Helm 4. The API image runs Helm 4.3.1 (0.6.x: 3.16.0) for the releases RunR installs on the
    region clusters, and CI checks the chart with it. RunR applies and waits for those releases as
    Helm 3 did (--server-side=false, --wait=legacy, --rollback-on-failure for --atomic): an
    existing region's releases upgrade as before, a region added now gets them the same way, and
    nothing has to be done. The chart installs and upgrades with Helm 3 or Helm 4; with Helm 4 an
    upgrade of a release installed with Helm 3 stays client-side, and a new install is server-side
    (docs/upgrade.md).
  • The API reference (/api/docs, /api/docs.json) is built with Scramble 0.13: the same 687
    operations, now in an OpenAPI 3.1.2 document. The success responses of 304 operations say more
    (the items of their lists, the fields of their objects, constant values; 50 of them read only
    string or object before), the GitHub, GitLab and SAML callbacks answer 302, and the traces'
    endpoints have their success responses. The API takes Laravel Tinker 3 and laravel-modules 12 (the modules'
    configuration has the new generator keys; the modules are unchanged).
  • The Python MCP starter runs on the MCP Python SDK 2. server.py of a new Python MCP server
    (Projects → New MCP server → Python, mcp_server_create) uses MCPServer, FastMCP's name in
    SDK 2, and its requirements.txt asks for mcp>=2.3,<3; the tools, the gateway signature check
    and the caller's identity work as before, and 2025-era MCP clients are still served. A server
    made from the earlier starter keeps its own files and SDK 1; to move it, compare it with
    examples/mcp/python. The TypeScript starter takes Zod 4 (zod ^4.6.7
    with @modelcontextprotocol/sdk ^1.23.0); server.ts is unchanged.
  • The console's dependencies: Vite 8, Vitest 5, jsdom 31, vue-router 5, Pinia 4, Sentry 11,
    xterm.js 6 and the Lucide icons from @lucide/vue 1 (lucide-vue-next ended deprecated at
    1.0.0), with the minor and patch updates of its other packages. The console works as before:
    Alt+arrow in the project and sandbox shell still moves by word, a dev stack with
    VITE_SENTRY_DSN sends Sentry what it sent before, and seven icons have Lucide's redrawn
    shapes (the clock calendar, the check and help circles, the credit card, the key, the bolt).
    Building the console needs Node.js 22.12 or newer, its unit tests 22.22.2, 24.15 or 26.
  • The SDKs' development dependencies: the Sandbox SDK (Node) builds with TypeScript 7 and
    @types/node 26, the Workflow SDK (Node) also tests on Vitest 5 (development needs Node.js
    22.12 or newer); the published packages still run on Node.js 18 and their output is the same.
    The Python SDKs accept websockets up to 17 (Sandbox), test on pytest up to 9 and build with
    setuptools up to 84 (Workflow, whose license is now the SPDX expression MIT).
  • The Python SDKs require Python 3.11 or newer (runr-sandbox and runr-workflows:
    requires-python >=3.11; Python 3.9 and 3.10 are past their end of life); their classifiers
    name 3.11 to 3.15. Both pass their tests on Python 3.11, 3.13, 3.14 and 3.15, and on CI's 3.12.
  • The PyTorch weights example (examples/ai/hf-python/weights) pins transformers 5.22.2.
  • CI: Node.js 26 (the current LTS line) in every workflow, Kind v0.33.0, cloud-provider-kind
    v0.12.0, kubeconform v0.8.0 and crane v0.22.1, each with its checksum. The Kind suites (the weekly
    e2e and the dependency bot's) run the newest Kubernetes only: Kind v0.33.0's node image of
    Kubernetes 1.37.0, from the reqs mirror, with kubectl 1.37.2; the chart is checked with
    kubeconform against Kubernetes 1.30, the oldest RunR supports, and 1.37.
  • Go 1.27. Every module (the region agent, the queue consumer, gateway-auth, image-upload, the
    CLI, the Terraform provider, the dev stack's Sentry tunnel and the Q interpreter example) declares
    go 1.27.4, CI runs Go 1.27.4 and the images build on reqs/golang:1.27-alpine: go1.27.4 also
    carries the standard library's security fixes of go1.26.11 (cgo, the go command, the compiler,
    the linker, net/http). gateway-auth is 1.1.0 and image-upload 1.2.0 now, so the release
    builds both again.
  • The examples' images build on Node 24 and Python 3.15: the MCP starters' Dockerfiles
    (reqs/node:24-slim, reqs/python:3.15-slim) and the GPU CaaS example (reqs/python:3.15-slim).
    The mcp-node and mcp-python runtime templates take them too (reqs/node:24-slim,
    reqs/python:3.15-slim; the Python starter's mcp and uvicorn install on 3.15 from wheels). A
    runtime registered from a template earlier keeps its manifest: PUT /api/runtimes/{id} with the
    template's runtime_manifest (GET /api/mcp-servers/templates) moves it.
  • The supply-chain image runs Trivy 0.76 and cosign 3 (supply-chain:1.1.0; Trivy 0.76.2,
    cosign 3.1.4). Scans, SBOMs and the scanner DB mirror work as before (the same report schema,
    trivy-db:2 and trivy-java-db:1). cosign 3 signs into a Sigstore bundle with the public
    instance's transparency log by default; RunR signs with
    --use-signing-config=false --new-bundle-format=false --tlog-upload=false, so signatures and
    attestations stay the .sig and .att tags that policy-controller, the API and
    cosign verify --key … --insecure-ignore-tlog=true read. A patch feed of your own signed with
    cosign 3 needs the same flags (docs/security.md).
  • The Spin shim is containerd-shim-spin v0.27.2 (containerd-shim-spin:v0.27.2-runr.1, Spin
    runtime 4.2.6), built as before with the runwasi fix that gives a Wasm pod's Linux containers
    their own environment. A region with WebAssembly gets it from the region Job of the upgrade
    (region:reconcile): the wasm-installer replaces the binary on its nodes one at a time, without
    a container runtime restart (docs/wasm.md).

Fixed

  • The timed warmer and the kept-warm previous revision on Knative 1.21 and later. Since
    Knative Serving 1.21 the Revision's autoscaling annotations are copied onto its PodAutoscaler,
    and a value set on the PodAutoscaler alone is put back at once: the warmer's count and the
    blue-green previous revision's min-scale: 1 did not hold there. On a region with Knative 1.21
    or later RunR now sets them on the Revision (no new revision, no restart); before 1.21 it sets
    them on the PodAutoscaler as before (docs/scaling.md).
  • region:reconcile heals a registry Pending on a dedicated worker on newer Kubernetes. The
    scheduler of newer Kubernetes (1.35 and 1.37 tested) does not name the taint any more ("had
    untolerated taint(s)"), and the dedicated-worker-toleration step did not find the Pending pod
    of a component installed before its node became a dedicated worker. It reads both messages now.
  • A region created with the setup wizard records its Kubernetes version (POST /registry-setup/start), as POST /knative-regions does, so kubectl exec takes the region's
    minor from the start rather than after the first region:reconcile.
  • The admission policy's install no longer fails while policy-controller's webhook starts.
    Right after the install, its Deployment can be available before its Service has a ready
    endpoint, and the API server refused the ClusterImagePolicies with "failed calling webhook …:
    connection refused" (the region's admission status failed). RunR now waits for a ready endpoint
    of the webhook (up to 2 minutes) and tries a write the webhook could not be called for again,
    for up to 2 minutes; a settings change and region:reconcile do the same
    (docs/supply-chain.md).