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.

Pulumi Community

I’m not very familiar with ACR, but we’ve got this example that might help: <https://www.pulumi.com/docs/guides/crosswalk/kubernetes/apps/#build-and-deploy-a-container>

I notice it doesn’t use `imagePullSecrets`, so it may have something to do with the resource group or other permissions like that

that's using the built in support for ECR it looks like, and refers to the image directly instead of by repo/name

There’s a cloud provider switcher at the top of the page

would pulumi be ok if I wanted to manage it separately? i.e. it wont blow up if that resource already exists and its not in the current state?

I could use pulumi to manage it, but feel like the registry lives out the normal infra lifecycle

Right; pulumi won’t delete any resources you’re not explicitly managing

You can import existing resources to manage with pulumi, but it doesn’t happen by default

<https://www.pulumi.com/blog/adopting-existing-cloud-resources-into-pulumi/>

I think the big insight there is to declare a separate `docker.Image` that contains the login details :slightly_smiling_face:

hmm it looks like those samples build a local image before uploading - the `build` property is required

docs refer to the registry there as :
/**
     * Credentials for the docker registry to push to.
     */
    registry?: pulumi.Input&lt;ImageRegistry&gt;;

Again, I’m not very familiar with ACR, but their example doesn’t show an `imagePullSecret` either: <https://docs.microsoft.com/en-us/azure/aks/tutorial-kubernetes-deploy-application#update-the-manifest-file>

ahhh, they do it by 'attaching' the ACR: <https://docs.microsoft.com/en-us/azure/aks/cluster-container-registry-integration>

omg, problem was a missing `latest` tag (I thought it was added automatically by tooling) - lead to unauthorized instead of 404