InfrastructureGitOps
Kafka → Terraform migration
- Company
- Adeva — Fashion Digital client
- Role
- Senior Site Reliability Engineer
- Period at the company
- Sep 2025 — Present
Problem
Fashion Digital client’s Kafka topics, ACLs and connectors were managed through an aging internal deployment tool with no version history, no diffing, and no safe way to review a change before it hit production.
Approach
Working with SRE and Cloud Engineering teams, I’ve co-architected a project to import every existing Kafka resource into Terraform state without downtime, using targeted imports and drift detection to make sure the generated configuration matched what was actually running. Once the import was verified, I’ve retired the legacy deployment application and rebuilt the release path around pull request review and terraform plan/apply automation.
Impact
- Every Kafka resource across all environments is now versioned, reviewable and easy to be replicated.
- The outdated deployment application was fully deprecated.
- Environment promotion is now handled by Terraform plan diff instead of a manual, undocumented change.
Tech stack
TerraformKafkaGitHub ActionsKustomize