07/03/2020, 7:31 AM
does anybody know why k8s.helm.v2.Chart destroys its resources one by one, not in parallel and if that could be fixed? it takes much more time than needed with many manifests in the helm chart
I've found the answer to this, it seems it's not about the provider itself, but just about ineffective s3 state handling