Are most folks using Pulumi's Helm capability stil...
# kubernetes
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.
@steep-toddler-94095 what's your general procedure when you encounter this using
Copy code
kubernetes:<|> (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?
Copy code
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
Get Fluent Bit build information by running these commands:

export POD_NAME=$(kubectl get pods --namespace fluent-bit -l "<,|,>" -o jsonpath="{.items[0]}")
kubectl --namespace fluent-bit port-forward $POD_NAME 2020:2020
curl <>
got it stuck, basically... oops
Copy code
helm rollback fluent-bit --namespace fluent-bit
Rollback was a success! Happy Helming!
I wasn't anticipating this working, but it did... 🎉
yeah you can interact with this resource as if you installed it with
. 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