wooden-ice-60753
12/16/2022, 6:45 PM.Release.IsInstall
built-in object for helm. I'm currently using k8s.helm.v3.Chart for the deployment. It seems that it always sets .Release.IsInstall
to true
and .Release.IsUpgrade
to false
. k8s.helm.v3.Release does set these values right.
I'm in a bind. Either I need to get it working for k8s.helm.v3.Chart or switch to k8s.helm.v3.Release. For the former, I'm coming up empty. For the later, there isn't any docs on that. Just swapping the Chart to Release doesn't work gracefully because pulumi will try to delete resources at the same time helm will try to create resources with the same name.
Any tips?victorious-church-57397
12/16/2022, 7:21 PMwooden-ice-60753
12/16/2022, 8:20 PMx
in the chart simple
. The pulumi apply
will spit out resource simple/x was not successfully created by the Kubernetes API server : statefulsets.apps "x" already exists
. I need the delete to happen first. This is not implemented.
I'm iffy about running pulumi destroy --target
. That would solve the simultaneity problem. (I'm lucky that the resource isn't in a dependsOn
block of another resource. I had a different issue once like this and when the resource is in a dependsOn block of another component, selectively deleting it is difficult).victorious-church-57397
12/16/2022, 8:31 PMcuddly-computer-18851
12/17/2022, 10:19 AMwooden-ice-60753
12/17/2022, 8:07 PMisUpgrade
flag to the code. (I have that coded up.) Don't see a way to find out whether something actually is an upgrade (if the k8s.helm.v3.Chart resource is new or being updated). Any clues?