This message was deleted.

I've also considered just separating out cluster-specific stuff into another project, though I'm not sure which is the best practice

@adamant-terabyte-3965 Pulumi drives towards a desired state. In this case, you’ve defined something in your pulumi program, and it doesn’t exist in Pulumi’s state. When something doesn’t exist in Pulumi’s state, Pulumi assumes it needs to be created. If it exists in the cloud provider, you’ll get the error you’re seeing To fix this, you need to import the resource into Pulumi’s state so it knows about it. You can do this using an

import

resource provider or the

pulumi import

command: https://www.pulumi.com/docs/guides/adopting/import/

Oh great thank you! If I'm understanding the import ID's correctly, do I need to export the import ID when I create that resource, or go into the Pulumi state in order to find it?

The import id is just the resource name. It should be namespace/name

thank you!