Don't use k8schain, statically link cloud cred helpers in cosign #1279
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
cosign
binary size does not change (~88MB) -- it actually get slightly smaller by about 12 KB.k8schain
depends on an unmaintained fork of kubernetes code in order to pick up cred helper logic for GCR/ECR/ACR. Instead, we can statically link the code that powers ECR/ACR cred helpers, and include ggcr's equivalent keychain.This doesn't remove the k8schain dependency from the cosigned webhook validator, but a future change could fix that after/using google/go-containerregistry#1234
Release Note
cc @mattmoor