Skip to content

RunR 0.6.1

Choose a tag to compare

@brkfun brkfun released this 24 Oct 18:18
· 53 commits to main since this release
v0.6.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.6.1 is a maintenance release of 0.6.0: a redeploy is active within seconds again, as on 0.5.10; the console says when it cannot reach the server instead of "An error occurred."; and the console's in-app tutorial follows the 0.6.0 console again. It also gives tenants the tables of the Billing and Ticket modules while those are switched off. It adds no Helm values and no new database migrations. CHANGELOG.md has the complete history. Downloads, the Terraform provider registry and the documentation are on runr.sh.

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.6.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.6.1 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.6.1/) and attached below; check them against checksums.txt (docs/cli.md#install).
  • Terraform / OpenTofu: source = "runr.sh/brf-tech/runr", version = "~> 0.6". runr.sh serves the provider registry protocol; terraform init checks the archive against SHA256SUMS, signed with the RunR release key (key ID 2588846B241BC095) (docs/terraform.md#install).
  • GitHub Action: uses: brf-tech/runr/actions/deploy@v0.6.1; it downloads the CLI from runr.sh (docs/github-action.md).
  • Images: every image is published under ghcr.io/brf-tech/runr and pulls anonymously.

The documentation is at runr.sh/docs and in the documentation index here.

Upgrading from 0.6.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). From 0.6.0 nothing has to be decided or set: 0.6.1 adds no Helm values and no new database migrations; with tenancy, the migration Job runs the Billing and Ticket tenant migrations that 0.6.0 skipped while those modules were off (tables and columns only). Horizon works a new deploys queue with a worker of its own: an idle runr-horizon runs one more worker process (about 70 MB), which the chart's default memory limit covers (0.6.0 → 0.6.1 in docs/upgrade.md).

helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.6.1 -n runr --reuse-values
  • The region agent and the event gateway move to 0.6.1. As in 0.6.0, they run at the installed version: after helm upgrade returned, the Job runr-region-reconcile-<revision> moves the regions' agents (also the internal network's authz), queue consumers and topic publishers from agent:0.6.0 / queue-consumer:0.6.0 to ghcr.io/brf-tech/runr/agent:0.6.1 and queue-consumer:0.6.1; each rolls once. A region that pulls through a mirror of your own needs these two images there before the upgrade (Order of operations).
  • Back to 0.6.0: first let the running deploys finish, because 0.6.0's Horizon does not work the deploys queue (Rolling back to 0.6.0). Then helm rollback (or helm upgrade with the 0.6.0 chart where only one package version is kept) on the same database; the region Job of the 0.6.0 chart moves the region images back to 0.6.0. Never install 0.5.10 again on an installation whose project secrets were finalized (Rolling back to 0.5.10).
  • Terraform provider 0.6.1 has the resources and data sources of 0.6.0; version = "~> 0.6" picks it up with terraform init -upgrade.

From 0.5.10, upgrade straight to 0.6.1: 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 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.6.1 (2026-10-24)

Upgrade notes

No new database migrations and no new Helm values. With tenancy, the migration Job runs the Billing
and Ticket tenant migrations that 0.6.0 skipped while the module was off. Horizon works a new
deploys queue with a worker of its own. Before a rollback to 0.6.0, let the running deploys
finish: the 0.6.0 → 0.6.1 section of upgrade.md says how.

Fixed

  • The console's tutorial follows the 0.6.0 console. Its steps point at the current controls
    again (a step whose target was gone dropped out without a word; a unit test now checks every
    target and text) and show the create wizard's global projects, New MCP server, rightsizing,
    environments, rollouts, deploy strategies, the timed warmer and the settings pages' tabs; the
    edit modal gets a tutorial button.
  • The console says when it cannot reach the server. A request that got no answer (network
    down, DNS, a server certificate the browser rejected, CORS, a dropped connection) showed only
    "An error occurred."; it now says the console could not reach the server and to check the
    connection, and a timeout says the server did not answer in time. HTTP errors still show the
    API's message, cancelled requests stay silent. Deleting a deployment and saving the audit log
    retention show the API's message instead of "An error occurred." too.
  • Tour steps on buttons that appear on hover show the button. The deployment table's log,
    rollback and delete steps highlighted an invisible button; the step's element is shown while the
    step is active.
  • A tenant gets the tables of the Billing and Ticket modules while they are switched off. The
    entrypoint disables a module that is off, so its tenant migrations were never registered: a
    tenant created on 0.6.0 with billing off had no billing_* tables, and older tenants missed
    0.6.0's billing_cost_limits and queue consumer charging, against docs/billing.md
    ("the billing tables exist … also while the module is off"). Tenant schemas now take every
    module's tenant migrations, enabled or not.
  • A redeploy is active within seconds again. 0.6.0 added calls to the region's API server on
    the way from POST /deploy to an active deployment, one after the other and each on a new TCP
    and TLS connection: the replaced deployment's teardown (queued ahead of the deploy on Horizon's
    one idle worker), the secret values and the internal-network routes. Against a real API server
    a redeploy took 10-12 s instead of 4-5 s. The apply and the readiness checks now run on a
    deploys queue with a Horizon worker of their own (one more idle process in runr-horizon),
    calls to an API server reuse their connections, a new deployment is checked every second for
    its first 10 s, and the response cache no longer keeps a deployment "pending" after its
    activation (a GET during it was cached under the new version with the old row until the
    project changed again: 11-22 s in Kind). Kind with 100 ms added to the API server: 7.0 s on
    0.6.0 (6.1 s on 0.5.10) → 3.4 s, median; without it 3.5-3.7 s → 2.5 s.