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 can docker pull my image from the terminal successfully.

there is nothing special about Pulumi’s treatment of Kubernetes. If your cluster can’t get to ECR, it will fail to pull the image.

In other words, we’re submitting entirely normal `Deployment` objects to the API server. If they don’t work here, they don’t work in Kubernetes YAML either.

This may not be in the scope of Pulumi but is there a doc that describes how to give minikube access to your local docker repo? Seems useful for local testing.

<@UCZ0LS7NZ> no, and actually I’m not entirely sure how to do that.

I’m guessing you don’t happen to know how to do it?

There's some ideas that have potential here: <https://stackoverflow.com/questions/42564058/how-to-use-local-docker-images-with-minikube>

I'm more curious how people are developing things locally. Or maybe people don't do that?

For most companies, it’s not feasible to use minikube for development, because most companies can’t boot mocked versions of every service. So in practice it’s much easier to use dev clusters.

minikube is great for getting started and learning though

<@UCZ0LS7NZ> Maybe <https://kubernetes.io/docs/concepts/containers/images/#referring-to-an-imagepullsecrets-on-a-pod> ?