Google Cloud Container Registry (GCR)

Google Cloud provides a container registry. Google Container Registry can be configured in Octopus as a Docker Container Registry Feed.

Adding a Google Container Registry to Octopus

1. To enable Octopus to communicate with Google Cloud registries, the Cloud Resource Manager API must be enabled.
2. Create a JSON key file Google Cloud service account
3. In Octopus go to Library ➜ External Feeds and add a new feed with the following properties
   • Feed Type: Google Container Registry
   • Name: {{This one’s up to you}}
   • URL: https://[REGION]-docker.pkg.dev
   • Credentials: Google Cloud JSON Key
   • Google Cloud JSON Key: {{Upload your JSON keyfile}}

Adding an OpenID Connect Google Container Registry to Octopus

Octopus Server 2025.2 adds support for OpenID Connect to GCR feeds. To use OpenID Connect authentication you have to follow the required minimum configuration.

To set up an OpenID Connect GCR feed:

1. Follow the Google cloud documentation to create and configure a Workload Identity Federation.
2. Set the IAM access control on your Artifact Registry following the access control instructions.
3. In Octopus go to Library ➜ External Feeds and add a new feed with the following properties
   • Feed Type: Google Container Registry
   • Name: {{This one’s up to you}}
   • URL: https://[REGION]-docker.pkg.dev
   • Credentials: OpenID Connect
   • Subject: Please read OpenID Connect Subject Identifier for how to customize the Subject value
   • Audience {{The audience set on the workload identity provider}} This should match the audience set on the Workload Identity Federation. By default this is https://iam.googleapis.com/projects/{project-id}/locations/global/workloadIdentityPools/{pool-id}/providers/{provider-id}

Help us continuously improve

Please let us know if you have any feedback about this page.

Send feedback

Page updated on Monday, April 14, 2025