Add logic to detect and use ambient OIDC from exec envs. #644
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.
This is based on some work I have been doing here: https://github.com/mattmoor/oidc-magic
At present, it is fairly tedious to use the "keyless" flow inside of environments that have a form of ambient OIDC (e.g. GKE workload identity). For example, in the context of Tekton, one needs to overlay
cosign
on an image likedocker.io/google/cloud-sdk:slim
, and then during execution have the step do something like:This change adds support for detecting when
cosign
is executing within an environment with this kind of ambient authentication, and automatically producing one when-identity-token
is not specified (andCOSIGN_EXPERIMENTAL=true
).This means the same signing can now be done with:
This is much simpler, but also the image will be both smaller (distroless) and more portable (not just GCP, but any provider we link).