Sambhav Kothari

kpack hardcodes the lifecycle config map name

1

As a part of testing the helm chart release in #686 I realized that kpack currently hardcodes the lifecycle config at https://github.com/pivotal/kpack/blob/ed7fe5056666f0ec1aa4378c92db1d52a0a872c5/cmd/controller/main.go#L160 This makes it hard to provide arbitrary configmap...

Add support for sigstore/cosign

8

https://github.com/sigstore/cosign is a project from sigstore. Instead of relying of a separate service/notary, it can directly push signatures to the OCI registry signed using a key. This might be a...

Have a controller env variable to display builds with build numbers instead of shas

1

I would be interested in users being able to see the output image with the build tag instead of the SHA. This could be a switch on the controller side...

Allow source polling to be turned off on an image basis

4

Images could possibly have an annotation/spec field that avoids triggering builds if the repo ref is changed Use case - Instead of polling git, users can use kp CLI to...

The kpack webhook hardcodes a bunch of values. These could be passed as config - for eg - https://github.com/tektoncd/triggers/blob/a545f76e7f0021ee13a1c22b6703dae18d2639fa/cmd/webhook/main.go#L104 See https://github.com/knative/eventing/issues/4530

Add a helm chart for kpack

6

It will be useful to have a helm chart for kpack deployments.

Detect the right version of platform api to use

10

### Description With the PR #1088 we allow users to provide a custom lifecycle image name. Previously we used to have pack select the appropriate lifecycle version based on the...

Add image/information to our dockerhub repo

3

### Description The Cloud Native Buildpacks Docker Hub repos (buildpacksio and (cnbs)(https://hub.docker.com/u/cnbs)) look pretty sketchy. cnbs is understandable, given that it seems like we only host sample/internal images (though we...

Allow pack to build applications that have their source code at a remote location

9

### Description A lot of the times, source code could be at remote locations such as git repos, blob stores as tarballs etc. It would be nice if we could...

Add support for `snapshot` as a qualifier for deb purls

6

`snapshots` are a way to refer to a series of packages from a give date. More details can be found at https://snapshot.debian.org/ The idea being that `distro` along with `snapshot`...