3 ms·
We switched to Pulumi from terraform for a new project because we can use it for both cloud infrastructure and for k8s configuration. It is easy enough to just
by gregwebs 7y ago
We switched to Pulumi from terraform for a new project because we can use it for both cloud infrastructure and for k8s configuration. It is easy enough to just apply k8s configuration files you have, but it is harder to delete the k8s resources in all places when you delete a k8s configuration file.
Operationally they can be thought of as working in exactly the same way: they compare desired configuration, already applied configuration, and observed configuration.
- MuffinFlavored 7y agoHow does it stack up to Terraform?
- gregwebs 7y agoAs a first impression it is more user friendly. The support for working with secrets is nice, but on the other hand it doesn't come free with locking support. We need more time to evaluate the stability.
- mwcampbell 7y agoDo you also build container images through Pulumi, or do you do that separately through your CI system? Also, do you use Pulumi in your developer inner loop, or something else?
- gregwebs 7y agoWe build images in CI and reference that in Pulumi. Not sure what your question is, we use this to deploy an infrastructure environment that includes k8s.
- darkwater 7y ago> We switched to Pulumi from terraform for a new project because we can use it for both cloud infrastructure and for k8s configuration. Did you think about using the kubernetes provider in Terraform to manage K8S as well?
- gregwebs 7y agoYes. Pulumi supports using existing yaml and helm templates (we aren't really using this yet), so I think it's support is better. But it may have been more influenced by the thought of having to deal with k8s boilerplate configuration in terraform's HCL. The team wanted something that was "easier to template', but I didn't want to use any template languages.