Hey all, so I'm looking at Pulumi as a tool to perhaps settle this interesting edge case described in the Terraform Kubernetes provider: https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#stacking-with-managed-kubernetes-cluster-resources - "Stacking with managed Kubernetes cluster resources". Now it appears to me the the underlying problem in Terraform is that providers are not lifecycled in a similar manner to the resources they control. Question is, is this behaviour different in Pulumi?

I've read the tf doc a couple times now and think i'm understanding what they're saying, but yes - it's very common to bootstrap a cluster and the resources in it inside the same stack/program

the work-around in Terraform is an interesting read - for AKS at least: https://github.com/hashicorp/terraform-provider-kubernetes/blob/main/_examples/aks/README.md - but it strikes me as quite the cludge. Surely treating Providers with lifecycle similar to resources would resolve such issues.

Pulumi's provider model is different, you can set specific providers for each individual resource, it's a much cleaner model