search

bitcoin-dev-project / warnet

Monitor and analyze the emergent behaviors of Bitcoin networks
https://warnet.dev
MIT License
92 stars 35 forks source link

"warnet down" takes a long time for large network #527

Closed pinheadmz closed 1 month ago

pinheadmz commented 1 month ago

I think its because we are "helm uninstall"-ing one tank at a time in a loop. I know it won't work with "default" namespace but for sure, namespace delete worked a LOT faster

josibake commented 1 month ago

Might be possible to tune our helm commands a bit, but also doing a namespace delete should work. One thing to keep in mind: if we deploy stuff with helm and then delete it with something else, we might leave helm in a confused / borked state.

pinheadmz commented 1 month ago

we learned in italy that we cant delete the default namespace

willcl-ark commented 1 month ago

Helm has state?

I thought it was a yaml masher only?

willcl-ark commented 1 month ago

I think I have something for this, inadvertently discovered when trying to teardown my Caddy deployment...

josibake commented 1 month ago

It would be great to speed up warnet down but I don't think this is a priority before Tabconf, unless we are talking about wait times that make development and testing unbearable.

I'd also suggest we investigate tuning helm first before going straight to managing the teardown ourselves in python.

willcl-ark commented 1 month ago

https://github.com/BarelElbaz/helm-delete-all

If we really want this to be faster, this plugin may be a solution

pinheadmz commented 1 month ago

closed by #550