Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of cert-manager and Volatility — release velocity, themes, recent moves, and the top alternatives to consider.
cert-manager's 1.21 line is about failure handling: backoff caps, renewal policies and clearer auth errors
cert-manager is running the 1.21 pre-release train through alpha.0, alpha.1 and now beta.0. The changes cluster around what happens when certificate issuance goes wrong: a configurable cap on CertificateRequest retry backoff, a new AuthFailed issuer condition that separates bad Venafi credentials from transient infrastructure failures, and certificate renewal policies.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
The 2.26.0 release was explicitly aimed at functional parity with the archived Volatility 2, landing around twenty plugins at once across Linux, macOS and Windows. Since then the work has shifted from filling gaps to structuring what exists: malware-specific plugins moved under a malware namespace with the old names deprecated, an arrow/parquet output renderer added, volshell given breakpoints, and per-release additions like sockscan, process_spoofing, pebmasquerade and etwpatch.
cert-manager is running the 1.21 pre-release train through alpha.0, alpha.1 and now beta.0. The changes cluster around what happens when certificate issuance goes wrong: a configurable cap on CertificateRequest retry backoff, a new AuthFailed issuer condition that separates bad Venafi credentials from transient infrastructure failures, and certificate renewal policies.
This is a reliability and observability cycle rather than a feature cycle. The recurring theme is making cert-manager's failure states legible — distinguishing permanent from transient errors, bounding retry storms, and letting Helm's common labels propagate into the ACME solver resources it creates on the fly. CAInjectorMerging reaching GA and deprecated API removal point to a line that is consolidating.
Expect a 1.21.0 release candidate next, with the renewal policy work being the piece most likely to change shape before it stabilises.
The 2.26.0 release was explicitly aimed at functional parity with the archived Volatility 2, landing around twenty plugins at once across Linux, macOS and Windows. Since then the work has shifted from filling gaps to structuring what exists: malware-specific plugins moved under a malware namespace with the old names deprecated, an arrow/parquet output renderer added, volshell given breakpoints, and per-release additions like sockscan, process_spoofing, pebmasquerade and etwpatch.
Two things are happening at once. The plugin catalogue keeps growing on the Linux side in particular — tracing, kallsyms, ftrace, VMA scanning, smearing protection — reflecting where memory forensics currently has the least coverage. And the framework is being made into something other tools consume: structured output formats, a shipped Windows executable, a namespaced plugin taxonomy with a year-long deprecation window. The project is treating plugin names as an interface it owes users stability on.
Expect the malware namespace migration to complete as the deprecated names age out, and the Linux plugin surface to keep taking the bulk of new additions, with output-format work continuing to open the framework to automated pipelines.
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 cert-manager or Volatility.
The public feed carries tags and image manifests; the release notes live in Prime docs.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
Patch tags land monthly with release notes that itemize nothing.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
See all cert-manager alternatives → · See all Volatility alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cert-manager and Volatility are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. cert-manager and Volatility are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top cert-manager alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "cert-manager alternatives" section above for the current picks, or visit /alternatives/cert-manager for the full list with editorial commentary on each.
Top Volatility alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Volatility alternatives" section above for the current picks, or visit /alternatives/volatility for the full list with editorial commentary on each.