This message was deleted.

sparse-intern-71089

12/13/2021, 12:24 PM

This message was deleted.

quiet-wolf-18467

12/13/2021, 12:27 PM

If it’s a GKE cluster, then the default permissions do include the ability to pull from GCR

some-continent-7311

12/13/2021, 12:31 PM

hmm, for some reason when I made the registry private and did

pulumi up

on one of the microservices it resulted in the

ImagePullBackoff

state of the pod

some-continent-7311

12/13/2021, 12:33 PM

… yep, it’s a GKE cluster

some-continent-7311

12/13/2021, 12:40 PM

thanks for your reply rawkode

some-continent-7311

12/13/2021, 12:47 PM

oh, just realized that GKE is pulling from a GCR in a different project @quiet-wolf-18467

green-school-95910

12/13/2021, 12:48 PM

You can set the service account used by the node pools (it defaults to the compute service account) Grant that service account permission to read and list files on the respective bucket on the other project

green-school-95910

12/13/2021, 12:49 PM

Are u using the google-native or the classic provider? I can send more specific links the docs

some-continent-7311

12/14/2021, 8:23 AM

Hi Luiz, I believe we are using the classic provider.

some-continent-7311

12/14/2021, 8:45 AM

I followed your advice about service account permissions and it works!

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.