4 ms·
My team has a lot of practical experience with Pulumi, after using custom bash scripts, manually-managing AWS config, some Terraform and CloudFormation in the p
by matharmin 6y ago
My team has a lot of practical experience with Pulumi, after using custom bash scripts, manually-managing AWS config, some Terraform and CloudFormation in the past. We use it for dozens of services on Kubernetes and AWS.
While we did have to write some of our own tooling to reduce the boilerplate over different services, Pulumi has been by far the best tool we've found to do the deployments. Being able to automatically provision a resource in AWS, then use results from that in a Kubernetes service (env var) in the same deployment, is not something I ever expected to be able to automate.
We haven't had any issues with module availability (I think it uses/adapts Terraform modules to a large extent).
The config as code feels way more approachable and reusable than any other tool I've seen.
I've never had any production issues because of Pulumi. It also allows you to preview changes before applying them, giving a nice confidence boost in the changes.
- sciurus 6y ago> Being able to automatically provision a resource in AWS, then use results from that in a Kubernetes service (env var) in the same deployment, is not something I ever expected to be able to automate. FWIW we do that with a small amount of glue code in our deployment tool that takes terraform outputs and passes then as values into helm.
- pluies 6y ago> Being able to automatically provision a resource in AWS, then use results from that in a Kubernetes service (env var) in the same deployment, is not something I ever expected to be able to automate. Terraform does this very well too, using either the Kubernetes provider or the Helm provider.