Luca Berton

Hi, I'm Luca.

#

I've been writing infrastructure-as-code professionally since 2014 — first deploying Ansible at scale, now spending most of my days in Terraform and OpenTofu. I worked on automation at Red Hat; today I'm the founder and CEO of Open Empower. The rest of my time goes into writing, teaching, and answering the same Terraform questions people kept emailing me.

Terraform Pilot is where I publish what I actually use.

What Terraform Pilot covers

#

Terraform and OpenTofu for infrastructure you run yourself: on-prem hypervisors, homelabs and network devices, plus the move from Terraform to OpenTofu.

• On-prem, homelab and network gear: Proxmox VE, VMware vSphere, Hyper-V, Nutanix, XCP-ng, TrueNAS, Synology and Unraid, and Cisco, Juniper, Arista, MikroTik and SONiC devices.
• OpenTofu: installing it, migrating from Terraform, and the features Terraform does not have.

What this site is (and isn't)

#

It is a place to find:

• Tutorials I would have wanted when I was learning — examples that run, not the ones that compile but never work.
• Notes on Terraform and OpenTofu patterns from real engagements, with the trade-offs spelled out instead of hidden.
• Reviews of the books and courses I've used, including the ones I wrote.

It isn't:

• Listicles assembled by a language model. Every post here is something I built, broke, or had to debug at 2 AM.
• A funnel. There's a paid course catalogue if you want one, but most of what's worth knowing is in the free articles.

What I work on

#

• Terraform & OpenTofu — on-prem and homelab providers, network devices, modules, state management, and migrations between the two.
• Ansible — I wrote Ansible For VMware by Examples (Apress, 2022) and run Ansible Pilot.
• Cloud platforms — AWS, Azure, GCP, with a soft spot for AWS because that's where most of the real workloads I see actually live.

Getting in touch

#

• LinkedIn: linkedin.com/in/lucaberton
• GitHub: github.com/lucab85
• YouTube: @BertonLuca
• Email: info@terraformpilot.com

If you found a bug in an article or want to suggest a topic, the fastest route is email or a GitHub issue on the relevant repo. I read everything; I reply to most of it.