Kaniko appears to be unmaintained; review replacement candidates for container builds

[GavinPJK]

Lack of activity suggests that Kaniko is not actively being maintained currently - GoogleContainerTools/kaniko#3348

Kaniko is used for "container-build" steps across the catalog, so moving to a supported set of tooling (e.g.: Buildah, shipwright) should be explored.

[JordanGoasdoue]

Hi @GavinPJK,

Thanks for raising this, it’s an important topic.

You’re spot on. We’ve already started discussing Kaniko’s replacement during the last TOC meeting.

Shipwright came up as a strong option because of its flexibility with multiple backends (BuildKit, Buildah, Cloud Native Buildpacks, Kaniko) and its connection to the CD Foundation, which makes it a good fit for what we’re aiming to achieve.

We’ll make sure to prioritize this as part of our 2025 roadmap for further exploration and planning.

Appreciate you bringing this up!

[msvticket]

After taking a closer look at Shipwright I'm sceptic regarding its fit for use in a pipeline run. It is implemented as an operator, so you need to create resources to get anything done.

I'm not sure that using one tool for all languages is the wisest route. For example goreleaser has (that we already use for building go binaries) have support for building images (with or without ko).