https://pulumi.com logo
#general
Title
# general
e

early-intern-90238

07/21/2019, 4:05 PM
its almost like its trying to connect to minikube for some reason
w

white-balloon-205

07/21/2019, 4:06 PM
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?
e

early-intern-90238

07/21/2019, 4:09 PM
what I think I need to do is completely reinitalize the stack
is there a way to do that?
it looks like its confused, doesn't know I switched GCP projects so its expecting the stack in Pulumu to line up
w

white-balloon-205

07/21/2019, 4:10 PM
You can just create a new stack
pulumi stack init
and deploy into that stack with the new config you set there.
e

early-intern-90238

07/21/2019, 4:10 PM
yeah
but then I would lose all my history
which I guess is fine...
w

white-balloon-205

07/21/2019, 4:11 PM
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?
e

early-intern-90238

07/21/2019, 4:11 PM
well I deleted the old ones manually
w

white-balloon-205

07/21/2019, 4:11 PM
You mean outside of Pulumi?
e

early-intern-90238

07/21/2019, 4:11 PM
so thats why I am in this pickly
yes
w

white-balloon-205

07/21/2019, 4:12 PM
I see.
e

early-intern-90238

07/21/2019, 4:12 PM
I'll probably create a new stack
delete my current one
I have to take kids out but thanks for quick response
👍 1
w

white-balloon-205

07/21/2019, 4:12 PM
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.
e

early-intern-90238

07/21/2019, 5:52 PM
thats a very good idea actually