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

Check your state, there’s an old provider in there I think. Pulumi state export and search for that version 

it sound like would be much better to recreate the stack

just updating or leaving single provider inside state hasn’t helped me or I broke the stack :slightly_smiling_face:

```     └─ pulumi:providers:kubernetes                          default_1_1_1           **failed**              1 error```

something requires that old provider, any idea how to find it? … going to enable resource one by one

There isn't always something that requires the old provider. If there was a recent provider update, the old provider is needed until all the resources have been updated; I don't think it gets "cleared out" until the `up` after the update completes.

<@UCWG26BH7> crd2pulumi was taking very old provider, will do the investigation a bit later