I'm running pulumi operator v2, and I was testing ...
# kubernetes
h
I'm running pulumi operator v2, and I was testing deleting the stack CR. I noticed that it did trigger a destroy of the stack, but if that operation failed, it will still go ahead to delete the stack CR and the pods, but leaving the provisioned resources as is (so not actually running
pulumi destory
). Is this expected?
More specifically, the failure I ran into was aws s3 bucket permission failure (because this was in a test environment, and my testing aws creds expired) So
SelectStack
failed