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

Are most folks using Pulumi's Helm capability still using Emulated resources, or Native releases? Wasn't sure if there was a reason to use native releases unless one wanted to remain interop with existing Helm rollout/deploy systems in ones' infrastructure?

i'm using native. it keeps the statefile smaller and reduces the calls made out to the k8s api server, and upgrading is basically 'blindly' following the official chart directions

Good points - perhaps for many community off-the shelf charts that is a good idea so one doesn't run into weird support problems.

<@UPL75DDUY> what's your general procedure when you encounter this using `Release()`?
```  kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (fluent-bit):
    error: another operation (install/upgrade/rollback) is in progress```

I know when helm I'd just roll it back, since this happened from a bad interrupt -- will helm just work naked with this resource since the state is stored in the helm release secret?

```helm status fluent-bit --namespace fluent-bit
NAME: fluent-bit
LAST DEPLOYED: Fri Feb 10 14:33:49 2023
NAMESPACE: fluent-bit
STATUS: pending-upgrade
REVISION: 3
NOTES:
Get Fluent Bit build information by running these commands:

export POD_NAME=$(kubectl get pods --namespace fluent-bit -l "<http://app.kubernetes.io/name=fluent-bit,app.kubernetes.io/instance=fluent-bit|app.kubernetes.io/name=fluent-bit,app.kubernetes.io/instance=fluent-bit>" -o jsonpath="{.items[0].metadata.name}")
kubectl --namespace fluent-bit port-forward $POD_NAME 2020:2020
curl <http://127.0.0.1:2020>```

got it stuck, basically... oops

```helm rollback fluent-bit --namespace fluent-bit
Rollback was a success! Happy Helming!```
I wasn't anticipating this working, but it did... :tada:

yeah you can interact with this resource as if you installed it with `helm`. but possibly adding the `atomic: true` flag might prevent this type of situation from happening in the future?

Yeah I was using atomic and wait with helmfile... probably should put those flags on the Release as well