Hello! Thanks for the fine work on Apko and the Chainguard open source tooling in general. I very much appreciate all that you have created so far.
We currently use Apko in Github Actions to push images/sboms to Google Artifact Registry. The action is authenticated via Workload Identity Federation using the auth and setup-gcloud Google actions.
Since the latest release, v0.11.3, we've received permissions errors on push to the registry. Using prior releases works as expected. I think I was able to track down that dropping support for Cloud Keychains in #732 may have been the source of this? Is there a workaround to continue to utilize Apko to push directly to a cloud registry in this way?
I understand maintaining support for every cloud registry/toolchain can be a burden, but I'd appreciate any guidance you all have in supporting this use case. Thanks!
Hello! Thanks for the fine work on Apko and the Chainguard open source tooling in general. I very much appreciate all that you have created so far.
We currently use Apko in Github Actions to push images/sboms to Google Artifact Registry. The action is authenticated via Workload Identity Federation using the
auth
andsetup-gcloud
Google actions.Since the latest release,
v0.11.3
, we've received permissions errors on push to the registry. Using prior releases works as expected. I think I was able to track down that dropping support for Cloud Keychains in #732 may have been the source of this? Is there a workaround to continue to utilize Apko to push directly to a cloud registry in this way?I understand maintaining support for every cloud registry/toolchain can be a burden, but I'd appreciate any guidance you all have in supporting this use case. Thanks!