https://pulumi.com
Join Slack
This message was deleted.
# kubernetes
s
This message was deleted.
k
I think the other option is to import resources via 
pulumi import
https://www.pulumi.com/docs/guides/adopting/import/
This would have to be done for each resource
l
hmm
Feels like it would make sense for Pulumi to add some annotations to resources so that re-importing is easier
or generally reconciling the state
k
Theoretically, that's what refresh should be for
so if there are resources marked as removed from pulumi but still in the cloud....
it's a bug?
l
Refresh should make the state reflect the actual state, right?
k
I think so
certainly by my reading
l
Hm, I wonder if it’s because I changed the 
provider
k
that could present a problem, different cluster?
l
Same cluster, but I moved from explicit named provider to the default provider
configured by 
config set kubernetes:…
It’s probably because I’ve done too much at once
I might have a play around and test some of the failure scenarios, manually change state, etc.
k
quite possibly, unfortunately, pulumi is still a relatively immature product and definitely has some rough edges
l
I’m using Pulumi mostly for services where I could just recreate them without issue at the moment, but I want to be confident enough to use it for our prod systems
yeah
k
but it's oh so productive 🤗
l
It’s a dream compared to the nightmare that is Helm
And the fact I can still use helm charts and provide them typed values 🤯
k
oh yeah, it really is a superpower 😄
3 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by