Deprecate gcr.io/k8s-skaffold/pack usage to official CNB image at docker.io/buildpacksio/pack

[aaron-prindle]

Skaffold hosts a container image for running the Cloud Native Buildpack (CNB) project's pack command at gcr.io/k8s-skaffold/pack. We have tagged images for each version of pack that we have packaged in this way. Our pack image was created to enable building with Buildpacks on Google Cloud Build. The source is found at: https://github.com/GoogleContainerTools/skaffold/tree/main/deploy/buildpacks

As the CNB project now maintains and distributes their own image (docker.io/buildpacksio/pack), we should deprecate Skaffold's pack image and move our users to the CNB-maintained image.

Related - go/deprecate-skaffold-pack-image

[jama22]

+1 the GCP buildpacks project would find that valuable. The current images under grc.io/k8s are a bit old and we'd prefer to stay up to date with the OSS community's version of pack.

[aaron-prindle]

I have bumped the gcr.io/k8s-skaffold/pack image to use pack v0.28.0 (the latest release, released Dec 6th 2022 - https://github.com/buildpacks/pack/releases/tag/v0.28.0). Previously we were using v0.21.1. This should resolve any issues in the short-term. In the long term we plan on finalizing our migration/deprecation doc and telling our end users to move to https://hub.docker.com/r/buildpacksio/pack

[steren]

Many users who used Cloud Run "setup Continuous Deployment" experience will have gcr.io/k8s-skaffold/pack in their cloudbuild.yaml. We should weight the pros and cons of asking them to migrate. Personally, I'd advocate instead for gcr.io/k8s-skaffold/pack to be a mirror of the official pack image.