LoginSign Up
← Back to all sparks
K

Kaniko

INFRA · APIS
Velocity0.0

Tool for building container images from a Dockerfile inside a container or cluster

github.com/GoogleContainerTools/kaniko ↗

Kaniko's release feed stops dead in June 2024 after a patch that undid its own change

container-buildsdockerfilekubernetesmaintenance-moderegistry-auth
◆Current state
Kaniko builds container images inside a container without a Docker daemon, and its release feed reads as a project in late-stage maintenance that then simply stopped. Every entry in this window carries the same boilerplate header of executor, debug and slim image tags, and underneath it the substance is dependency bumps, CVE-driven upgrades, and narrow fixes to ADD and COPY semantics. The last release here, v1.23.1, is a revert of behaviour changed weeks earlier plus documentation clarifying what the flag was supposed to do.
◆Where it's heading
The cadence tells the story: nine releases between December 2023 and June 2024, then nothing at all in the two years since. Even during the active stretch the work was defensive — registry-map compatibility, ECR authentication breakage, tar.gz handling in ADD, vulnerability scanning added to the executor image — rather than any expansion of what Kaniko does. The one recurring theme with forward motion, registry mirror and registry-map support, was about surviving locked-down or mirrored registry environments.
◆Prediction
Nothing in these entries points at planned work, and a two-year gap after a revert-and-document patch is the signature of a project no longer being released; anyone depending on it should assume the last published executor image is the last one.

◆Recent moves

  1. 2y ago

    Kaniko 1.23.1 reverts --no-push cache behaviour

    A patch that undoes a recent behaviour change so --no-push still pushes intermediate cache layers, and documents what --no-push and --no-push-cache are each meant to do. It is the last release in the feed, which makes a revert-plus-clarification the project's final published act.

    View source ↗
  2. 2y ago

    Kaniko 1.23 adds --chmod for ADD and COPY, registry mirrors for the warmer

    The most substantive release in this window: --chmod support on ADD and COPY closes a long-standing Dockerfile compatibility gap, and registry mirror support in the warmer's registry map extends the mirrored-registry work that runs through several of these releases. Both are about matching what builders already expect rather than new capability.

    View source ↗
  3. 2y ago

    Kaniko 1.22 adds path regmaps, fixes multi-file COPY into ENV paths

    Path-aware registry maps continue the mirrored-registry thread, alongside fixes for COPY into an ENV-specified path with multiple files and query-parameter handling in ADD. Steady Dockerfile-compatibility repair work, which is where most of Kaniko's late effort went.

    View source ↗
  4. 2y ago

    Kaniko 1.21.1 bumps dependencies to clear CVEs

    A pure dependency-refresh patch shipped six days after 1.21.0 to remove vulnerabilities present in that release. The pattern of a feature release followed quickly by a CVE-clearing patch repeats through this window.

    View source ↗
  5. 2y ago

    Kaniko 1.21 unpacks tar.gz in ADD, adds skip-TLS for private git

    Closes a two-year-old gap where ADD would not unpack a tar.gz archive, and adds a TLS-skip flag for private git contexts plus nightly vulnerability scanning of the executor image. The scanning addition is the clearest sign the project's priority had moved to keeping the shipped image clean.

    View source ↗
  6. 2y ago

    Kaniko 1.20.1 is documentation and dependency bumps

    README clarifications and version bumps for buildkit, docker and assorted transitive dependencies, with no user-visible behaviour change. Filler between the 1.20 and 1.21 releases.

    View source ↗