I ve reordered resources and taken dependencies on helm char

Question

I ve reordered resources and taken dependencies on helm charts rather than just crds in separate config groups and destroy got much further but was hanging for ages until finally failing with ```Diagnostics pulumi pulumi Stack k8s dev could not get token RequestError send request failed caused by Post dial tcp lookup on 192 168 65 5 53 no such host could not get token RequestError send request failed caused by Post dial tcp lookup on 192 168 65 5 53 no such host error update failed kubernetes appmesh system appmesh controller selfsigned issuer error Delete https REDACTED getting credentials exec executable aws iam authenticator failed with exit code 1 error post step event returned an error failed to save snapshot performing HTTP request Patch dial tcp lookup on 192 168 65 5 53 no such host Resources 199 deleted Duration 2h44m7s``` During the hang I checked resources and the aws appmesh controller and cert manager controllers had already been deleted I didn t think it would matter since I didn t see any finalizers or owner refs associated with the `` resource being deleted but maybe I m missing something Looks like this is due to

worried-city-86458 · Answer

This is what the resources look like in order of declaration and any explicit dependencies ```environmentNs Namespace environment config ConfigMap DependsOn = environmentNs environment sysctl ConfigGroup DependsOn = environmentNs kubePrometheusStackCrds ConfigGroup fluent bit Chart DependsOn = kubePrometheusStackCrds certManagerCrds ConfigGroup certManagerNs Namespace certManagerChart Chart DependsOn = certManagerCrds kubePrometheusStackCrds certManagerTest ConfigGroup awsLbcCrds ConfigGroup awsLbcChart Chart DependsOn = awsLbcCrds certManagerTest internal gateway ConfigGroup DependsOn = awsLbcChart finalizers environmentNs internet gateway ConfigGroup DependsOn = awsLbcChart finalizers environmentNs monitoringNs Namespace kubePrometheusStackChart Chart DependsOn = awsLbcChart finalizers certManagerTest kubePrometheusStackCrds prometheus adapter Chart DependsOn = certManagerTest kubePrometheusStackChart cluster autoscaler Chart DependsOn = kubePrometheusStackCrds external dns Chart DependsOn = kubePrometheusStackCrds appMeshCrds ConfigGroup appMeshNs Namespace appMeshChart Chart DependsOn = appMeshCrds certManagerTest appmesh ConfigGroup DependsOn = appMeshChart finalizers ackIamNs Namespace ack iam controller Chart``` It s proving to be essential to have a way to depend on a config group or helm chart and all it s children Failing that I need a way to get one of the child resources to explicitly depend on

worried-city-86458 · Answer

`certManagerTest` is my current attempt to wait until cert manager is ready to issue certs but it s not working so far

worried-city-86458 · Answer

I posted my <https github com pulumi pulumi kubernetes issues 861 issuecomment 881051795|workaround for cert manager> and after applying similar tricks elsewhere I can create and destroy my k8s stack without any issues