Channels
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
general
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
Powered by
#general
Title
g
glamorous-printer-66548
09/20/2018, 2:28 AM
I have a relatively big k8s pulumi stack (~10 microservices, each with a deployment and a service). When I run
pulumi destroy
it seems to run the deletion sequentially for each single resource and it is therefore really slow. Is this intentional / known?
m
microscopic-florist-22719
09/20/2018, 2:28 AM
This is intentional, yes.
@incalculable-sundown-82514
is actively working on improving this 🙂
(where improving means "enabling parallel deletion")
👍 2
Post