This message was deleted.

sparse-intern-71089

03/02/2020, 4:34 PM

This message was deleted.

gorgeous-egg-16927

03/02/2020, 4:49 PM

What would you suggest instead? It’s like this because users would frequently delete the k8s cluster in a separate stack, and then there was no way to clean up the resources that had been deployed to the cluster without manually editing state. Since the state is recoverable, we thought this was a reasonable compromise (warn prior to deleting from state).

limited-rainbow-51650

03/02/2020, 4:50 PM

See my comment on this GH issue: https://github.com/pulumi/pulumi-kubernetes/issues/881#issuecomment-593500282

limited-rainbow-51650

03/02/2020, 4:51 PM

I look at this as an intermittent network issue.

gorgeous-egg-16927

03/02/2020, 4:52 PM

The problem is we can’t tell the difference between a transient network partition and the cluster being deleted.

gorgeous-egg-16927

03/02/2020, 4:53 PM

Did you run a preview prior to applying the update?

limited-rainbow-51650

03/02/2020, 4:54 PM

Yes. it was ok then. Even the “preview part” of

pulumi up

was still OK

gorgeous-egg-16927

03/02/2020, 4:56 PM

Ah, I see. I didn’t consider the case where the partition occurred between preview and update

limited-rainbow-51650

03/02/2020, 4:57 PM

It’s like this because users would frequently delete the k8s cluster in a separate stack, and then there was no way to clean up the resources that had been deployed to the cluster without manually editing state.

This should be the exceptional case where users need to fiddle with state, not the normal behavior. I now feel punished for bad user practices of not removing their deployments before deleting the cluster. I now have to fiddle with state and my cluster manually.

gorgeous-egg-16927

03/02/2020, 4:57 PM

We should be able to recover your state, and I’ll open an issue to reconsider this behavior.

gorgeous-egg-16927

03/02/2020, 5:01 PM

If you are using the Pulumi Service, you can export older versions using

pulumi stack export --version <n>

or download it from the UI (we added this capability last week).

limited-rainbow-51650

03/02/2020, 5:03 PM

Can I list the versions via the CLI?

limited-rainbow-51650

03/02/2020, 5:08 PM

Or is the version the last part of the permalink posted after

pulumi up

gorgeous-egg-16927

03/02/2020, 5:08 PM

AFAIK, there’s no programmatic way to get the version currently (https://github.com/pulumi/pulumi/issues/2412#issuecomment-590125246) But yes, the version number is part of the permalink.

gorgeous-egg-16927

03/02/2020, 5:08 PM

So you’d want N-1

limited-rainbow-51650

03/02/2020, 5:10 PM

The faulty run was 68, so I exported 67. Do I now just import that version of the state again?

gorgeous-egg-16927

03/02/2020, 5:10 PM

Yes, that’s right.

pulumi stack import --file <file>

limited-rainbow-51650

03/02/2020, 5:12 PM

OK, I’m going to do that at home. I’m in the train at the moment via my mobile. That feels like doing surgery with a shaking hand. 😄

limited-rainbow-51650

03/02/2020, 5:12 PM

Thanks for the help!

gorgeous-egg-16927

03/02/2020, 5:13 PM

Sure thing. Let me know if you’re still having problems, and sorry for the inconvenience.

limited-rainbow-51650

03/02/2020, 5:14 PM

and I’ll open an issue to reconsider this behavior.

Just one last thing, can you @-mention me on the GH issue you would create so I can follow up?

👍 1

gorgeous-egg-16927

03/02/2020, 5:39 PM

https://github.com/pulumi/pulumi-kubernetes/issues/1013

60 Views

Open in Slack

Previous Next

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.