DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
A side-by-side editorial comparison of Kaniko and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
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.
Skipper tags a release per commit — nine in eight days, and none of them change routing.
Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.
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.
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.
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.
Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.
Nothing in these entries points to a direction change; the 0.27 line is in steady maintenance with supply-chain hygiene as the visible priority — oras-go pinned to a released version so osv-scanner stops flagging it, the CodeQL action upgraded, an OPA test hardened to deny requests with truncated bodies. The documentation change is the most revealing item: jwtValidation's behavior was unclear enough to prompt a proposed advisory, and the response was to clarify the docs rather than alter the code.
The tag stream will most likely continue at several releases a week with the same composition of dependency bumps and test fixes. These entries show no feature work in flight, so the next notable change is more likely another security-adjacent clarification than a new routing capability.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Kaniko or Skipper.
DNSControl is rewriting its record internals in public, one release candidate at a time
Fission's release feed carries only RC tags, and none of them say what shipped
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeePass-compatible password manager frozen mid-patch-run since 2021.
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
See all Kaniko alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Kaniko alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kaniko alternatives" section above for the current picks, or visit /alternatives/kaniko for the full list with editorial commentary on each.
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.