Sambhav Kothari

Hi @rszumlakowski my main use case is verifying that the images came from a specific kpack build cluster. I am hoping that the controller can be provided with the cosign...

A secret would be good enough that the controller can refer to if needed. The main issue here would be having this secret in the kpack namespace which normal users...

> > (the users who are in other namespace using the Image resource should not be able to access this private key) > > Can this be accomplished with kubernetes...

As discussed in the WG we cannot make this change directly since this is an end-user breaking change and the current implementation is mimicked by other platforms like kpack as...

@jromero I would prefer if we soften that warning. Since this is an end user change that we inadvertently implemented in both pack and kpack I would prefer we keep...

Related https://github.com/buildpacks/rfcs/pull/195 and https://github.com/buildpacks/pack/issues/268#issuecomment-973623399 @developer-guy perfect timing! We have been actively working to get cosign integration, along with sbom attestations integrated in the project! We would love to have contributors...

(Accidentally closed, reopened again)

There's a separate/related ticket at https://github.com/buildpacks/pack/issues/768 If we have a buildkit frontend - buildpacks could just "work" out of the box with docker.

Alternatively an easy way out that I use right now if put as many arguments as possible in `project.toml` to configure `pack` and run a `pack build ` and use...

What is the consensus on this issue - should it use the latest version by default or only the latest patch of a supported version or the latest version of...