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

Yes - that looks like something is trying to connect to minikube. 

Do you have kubernetes resources in your project?

How are you configuring your kubernetes provider?

If you do not provide any other configuration, the provider picks up your ambient context, which perhaps is minikube?

what I think I need to do is completely reinitalize the stack

it looks like its confused, doesn't know I switched GCP projects so its expecting the stack in Pulumu to line up

You can just create a new stack `pulumi stack init` and deploy into that stack with the new config you set there. 

What exactly is it you want to do?  What do you have in mind with “reinitalize the stack”?

Do you want to create new resources from scratch and delete the old ones?

I have to take kids out but thanks for quick response

You can `Pulumi state delete` each of the old resources that no longer exist or export the state file and remove them then re-import. 

That would allow you to keep moving forward with the same stack history. 