https://pulumi.com logo
Title
f

fresh-restaurant-12335

07/12/2021, 5:14 PM
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?
b

billowy-army-68599

07/12/2021, 5:24 PM
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
f

fresh-restaurant-12335

07/12/2021, 5:32 PM
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.
b

billowy-army-68599

07/12/2021, 6:05 PM
Pulumi's provider model is different, you can set specific providers for each individual resource, it's a much cleaner model
🙌 1