You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
whether to use the kubernetes keychain instead of the default keychain (supports workload identity).
This is a bit of a misnomer, since "the kubernetes keychain" as a term isn't particularly well defined, and because what I believe it means is, "the common set of cloud auth helpers that can be included in Kubernetes (i.e., GCP, AWS, Azure)", and in actuality, the flag enables a number of auth helpers that aren't exactly that set of "kubernetes auth helpers":
Description
The
--k8s-keychain
flag (e.g., incosign sign
) isThis is a bit of a misnomer, since "the kubernetes keychain" as a term isn't particularly well defined, and because what I believe it means is, "the common set of cloud auth helpers that can be included in Kubernetes (i.e., GCP, AWS, Azure)", and in actuality, the flag enables a number of auth helpers that aren't exactly that set of "kubernetes auth helpers":
cosign/cmd/cosign/cli/options/registry.go
Lines 83 to 89 in 516cc39
Along with GCP, AWS and Azure, this set includes the GHCR auth helper, and with #2007 this keychain will also include an Alibaba helper.
I propose changing this flag to something like
--workload-identity
(ideas welcome!) or at least improve docs to clarify what it does.The text was updated successfully, but these errors were encountered: