News for hackers. Stuff that matters.
Re:Terraform best practices for reliability at any scale by yellowapple on Friday August 04, 2023 @09:45PM (#37008152)
- In the event that you are working with different cloud providers, Terraform is one thing to learn that then applies to all of them, as opposed to learning each provider's bespoke infra-as-code offering. Most companies stick to one PaaS/IaaS, but individual personnel ain't necessarily as limited over the courses of their careers.

- Not all cloud providers have an infra-as-code offering of their own in the first place (especially true with traditional server hosts), whereas pretty much every provider with some sort of API most likely has a Terraform provider implemented for it.

- Terraform providers include more than just PaaS/IaaS providers / server hosts; for example, my current job includes provisioning Datadog metrics and PagerDuty alerts alongside applications' AWS infra in the same per-app Terraform codebase, and a previous job entailed configuring Keycloak instances/realms/roles/etc. via Terraform.

Re:Terraform best practices for reliability at any scale by androidbishop on Saturday August 05, 2023 @02:00AM (#37009388)
Also pretty neat that there's a Terraform provider for Kubernetes native resources.
Re:Terraform best practices for reliability at any scale by mcfedr on Saturday August 05, 2023 @07:35AM (#37011015)
Personally it's the only way to work with kubernetes. Terraforms change control is excellent. Cannot go back to helms upgrade and how it does what you want.