Digital Rebar v4.17 is out, and it takes the standard patterns and proven processes you already rely on and pushes them further. This update continues our goal in making the most demanding infrastructure operate with ease, at whatever scale you’re running it. Every feature in this release maps to one of four things that matter to operators:
Scale,
Speed,
Choice, and
Change.
Scale: Multi-Site Manager Gets Serious About Size
The Manager Replication Refactoring is complete in v4.17, and it changes how Multi-Site Manager handles distributed estates. Replication has shifted from an eager, streamed model to an on-demand, cached one. This requires a dramatically smaller memory footprint without giving up performance on the things operators do constantly, like navigating the UX. The target for this work is 50,000 servers under a single pane of glass, shaped directly by the operators running some of our biggest estates. If you’ve been curious about what Multi-Site Manager can actually handle, this is the release that answers that question.
Speed: EIKON Goes to Production, Portal Gets Sharper
EIKON, Digital Rebar’s native image deployment engine, reaches full production readiness in v4.17 and becomes the recommended path for image-based deployment. It’s the fastest, most repeatable way to provision infrastructure, handling whole-disk images and rootfs archives across LVM, software RAID, and stable device identifiers, with UUID-based fstab generation so boots don’t depend on disk enumeration order. It runs in airgap environments, supports authenticated image sources, and covers Debian, RHEL, and Windows Server 2019–2025 plus Windows 10/11 without version-specific handling. Because EIKON shares Curtin’s image-deploy parameters, moving to it is just a profile swap. Curtin has caused enough friction over the years; with EIKON production-ready, the image-deploy plugin is now deprecated. There’s no removal date set, we’re waiting on your feedback, not a calendar. The RackN Portal also gets a visual refresh in v4.17, including a new Dark Theme and configurable contrast and color options. It’s a straightforward improvement to how much information Digital Rebar surfaces at once, and how fast you can act on it.
Choice: Pipelines Recover Instead of Restarting
Pipelines are the heart of how Digital Rebar standardizes provisioning, and v4.17 makes them more resilient. Provisioning now runs through distinct, tracked phases, prepare, discover, hardware, operating system, application, and if a pipeline fails partway through, it resumes from that phase instead of starting the machine over. That’s less manual intervention and faster recovery at scale, without asking you to change how you already build pipelines.
Change: A Role Built for the People Running Day-to-Day Ops
v4.17 introduces the Operator role as the first entry in Role-Based UX, a streamlined, day-to-day view with less navigation and faster access to common tasks. It’s likely to become the daily driver for anyone running fleet operations, and it’s the first of several planned role-based views, with Administrator up next. We want feedback from the operators using it. Content Archive also reaches General Availability in v4.17, following a Technical Preview cycle in v4.16. It bundles object definitions, artifacts, and plugin extensions into self-contained, atomically upgradable packages, everything you need to start and run a data center, in one archive. That matters for security posture, bootstrapping, and disaster recovery, and it’s built on the same enterprise requirements that shaped Multi-Site Manager. One more operational detail worth knowing: if you’re using an external secret store (Vault, AWS Secrets Manager, Azure Key Vault) drpcli set now rotates the secret directly in that store instead of overwriting it with an inline copy, so the reference stays intact.
See It in Action
4.17 keeps extending the standard patterns and proven processes we’ve spent years building. If you want to see Multi-Site Manager, EIKON, or the new Operator role running against a real environment,
schedule a demo and we’ll walk through it with you. Have a request for a feature? Reach out to
success@rackn.com and let us know! Read the release notes here: https://docs.rackn.io/stable/resources/summaries/release_v417/
