Push a new release to a balena fleet and pin a canary group of devices to a draft release before promoting it fleet-wide

domain: docs.balena.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Build and push a new release with balena push <fleetName>, or build locally and deploy with balena deploy <fleetName>
  2. Add --draft to the build/deploy command so the release is created as a draft rather than auto-deployed to unpinned devices
  3. Pin a subset of canary devices to the draft release, which is reflected via the read-only device.is_pinned_on__release field in the balena API
  4. Monitor the canary devices for issues on the draft release
  5. Once validated, run balena release finalize <commitOrId> to convert the draft to a final release so it auto-deploys to all unpinned devices in the fleet

Known gotchas

Related routes

Pin a balenaCloud fleet to a specific release and use the Supervisor API to control service restarts on individual devices
docs.balena.io · 6 steps · unrated
Implement a device-fleet OTA strategy using canary deployments: stage updates to a small device cohort before full rollout
iot-general · 6 steps · unrated
Deploy container-based OTA updates to a device fleet using balenaCloud
balena · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans