Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use k8schain, statically link cloud cred helpers in cosign #1279

Merged
merged 2 commits into from
Jan 20, 2022

Conversation

imjasonh
Copy link
Member

@imjasonh imjasonh commented Jan 6, 2022

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

cosign CLI uses statically linked cloud cred helpers to authenticate to registries

cc @mattmoor

Signed-off-by: Jason Hall <jasonhall@redhat.com>
Signed-off-by: Jason Hall <jasonhall@redhat.com>
@mattmoor mattmoor merged commit 22007e5 into sigstore:main Jan 20, 2022
@github-actions github-actions bot added this to the v1.5.0 milestone Jan 20, 2022
mlieberman85 pushed a commit to mlieberman85/cosign that referenced this pull request May 6, 2022
…store#1279)

* Don't use k8schain, statically link cloud cred helpers in cosign

Signed-off-by: Jason Hall <jasonhall@redhat.com>

* Remove unnecessary nil check which was confusing linter

Signed-off-by: Jason Hall <jasonhall@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants