LoginSign Up
← Back to all sparks
W

werf

INFRA · APIS
Velocity5.0

GitOps delivery tool for building and deploying to Kubernetes

werf.io ↗

werf v3.x dev channel drops CNI for netavark networking while the 2.x alpha track holds to bug fixes

devopsgitopscontainer-buildskubernetesbuildahhelm
◆Current state
werf maintains two active release channels: a 2.x alpha series (at v2.78.2) focused almost entirely on correctness backports — stapel panics, cache repo handling, import failures on symlinked paths — and a v3.x dev series pushing new capabilities. The v3.x track added authenticated secret values in deploy pipelines, renderPatches support, and a hard networking dependency switch in v3.4.0-dev.
◆Where it's heading
The v3.x dev channel is where werf's actual evolution happens: embedded Deno for deploy scripting (v3.2.0), the netavark networking switch (v3.4.0), and a systematic race-condition fix campaign across build, deploy, and registry layers. The 2.x alpha track functions as a backport target for correctness fixes, not a destination for new features. Registry-side cleanup reporting and Helm surface improvements in 3.x suggest the team is hardening the GitOps workflow layer before calling v3 stable.
◆Prediction
The netavark switch in v3.4.0-dev is a hard breaking change — environments without netavark installed will lose rootless build capability. Expect migration documentation and a compatibility fallback discussion before any 3.x stable tag. The embedded Deno binary in 3.2.0 will likely gain more deploy scripting APIs once the networking layer stabilizes.

◆Recent moves

  1. 6d ago

    v2.78.2 [alpha]

    v2.78.2 [alpha] is a single-bug patch: stage push was re-compressing parent layers unnecessarily, inflating image sizes. No behavior change beyond corrected layer handling.

    View source ↗
  2. 7d ago

    werf v3.4.0-dev: netavark replaces CNI for rootless container networking

    v3.4.0 [dev] replaces CNI and slirp4netns with netavark as the required networking backend for rootless buildah-based container builds. This is a hard dependency change, not a soft preference — environments without netavark installed will break. The release also includes several build bug fixes including cross-external-base reuse being stopped incorrectly.

    View source ↗
  3. 7d ago

    v2.78.1 [alpha]

    v2.78.1 [alpha] fixes a single issue: stapel stage builds were incorrectly coupled to the stapel image catalog reference, which could cause unexpected build failures. Narrow correctness patch backported from v3.

    View source ↗
  4. 8d ago

    v3.3.1 [dev]

    v3.3.1 [dev] corrects the host-cleanup report to measure freed disk space from actual disk state rather than an estimate. Diagnostic accuracy fix with no behavior change in the cleanup logic itself.

    View source ↗
  5. 15d ago

    v3.3.0 [dev]

    v3.3.0 [dev] adds authenticated secret values in deploy pipelines and renderPatches support — two concrete additions to the Helm and deploy surface. These are the most substantive user-facing additions across several recent dev releases, bundled with build and host-cleanup correctness fixes.

    View source ↗
  6. 15d ago

    v2.77.2 [alpha]

    v2.77.2 [alpha] backports the stapel panic fix and cache repo misidentification fix from v3.3.0 into the 2.x stable track. Standard maintenance backport with no new functionality.

    View source ↗