Replace out of date publish images with cgr.dev equivalents.

[wlynch]

Changes

These should be drop in replacements with full shells.

Grype Output:

gcr.io/go-containerregistry/crane:debug	cgr.dev/chainguard/crane:latest-dev
1 Critical 5 High 10 Medium 11 Negligible 2 Unknown	1 Medium

golang:1.18.7	cgr.dev/chainguard/go:latest-dev
140 Critical 416 High 19 Low 337 Medium 452 Negligible 8 Unknown

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• [ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• [ ] Has Tests included if any functionality added or changed
• [ ] Follows the commit message standard
• [ ] Meets the Tekton contributor standards (including functionality, content, code)
• [ ] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• [ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• [ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[wlynch]

/kind misc

[imjasonh]

FWIW, it looks like gcr.io/go-containerregistry/crane:debug hasn't been updated since Mon Jul 31 2023 21:49:55, which is likely when the repo stopped having access to GCP. I don't know the current ownership of that project.

If there's interest, I think we could publish crane images to ghcr.io/google/go-containerregistry:debug where it can continue getting updates. Until then, the cgr.dev image is probably going to be the best place to get updates for now.

[Yongxuanzhang]

Cool! So the images are created and hosted by chainguard? How do they fix those vulberabilities?

[wlynch]

Cool! So the images are created and hosted by chainguard?

Yep! https://edu.chainguard.dev/chainguard/chainguard-images/overview/ for more details.

How do they fix those vulberabilities?

Magic 🧙 (really a lot of hard work and automation 💪 🤖 )

[vdemeester]

/retest

[vdemeester]

@wlynch @imjasonh still needed ? (if yes, it needs a rebase 🙏🏼 )

[afrittoli]

@wlynch ping 🙏

[wlynch]

rebased!

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester, Yongxuanzhang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [Yongxuanzhang,vdemeester]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment