Infrastructure

DevOps Projects

🚀 Professional Journey Overview Infrastructure as Code | Cloud Native Solutions | Continuous Delivery With 8+ years in DevOps engineering, I specialize in building scalable, resilient infrastructure and automating complex deployment pipelines. My expertise spans across multi-cloud environments, container orchestration, and implementing robust DevOps practices. 💼 Featured Projects 🔥 Current Active Projects Project: Hetzner Cloud Microservices Platform Timeline: 2024 - Present Type: Personal Technologies: Ansible, Terraform, Hetzner Cloud, GitLab CI, Podman, Packer, Devbox tool, Task framework Categories: infrastructure, automation, cloud Tags: #infrastructure #automation #cloud #hetzner #devops ...

My Career Journey

🚀 Career Timeline Each branch represents a role, and commits represent key skills or achievements acquired during that period. Legend Branch Color Role Period 🟢 career Main career timeline — 🔵 junior-dev@StartupX Junior Developer 2018–2020 🟠 backend-dev@MidCorp Backend Developer 2020–2022 Legend Branch Color Role Period 🟢 career Main career timeline — 🔵 junior-dev@StartupX Junior Developer 2018–2020 🟠 backend-dev@MidCorp Backend Developer 2020–2022 🟣 data-eng@AllianzTech Data Engineer 2022–2024 🟤 side-projects Side Projects Ongoing 🔴 sr-data-eng@SchwarzIT Sr. Data Engineer 2024–Now

Creating snapshot image in Hetzner with packer

On this entry we will cover how to create an new image in Hetzner Public Cloud by using Packer, as result we willl get a snapshot and then we can generate this new instance by using the snapshot created. Tools used so far: Ansible Packer hcl2_upgrade I did not create a repo yet because it will be the first part of a personal project I’m working on, hence I will provide a couple of templates below. ...

S3 by using random provider on Terraform

This is a piece of cake for most of you that are working on tf, I will drop this snippet code where you can create a S3 bucket with an unique name; as you know those requirements should fit in order to create the S3, hence we can use random_string, also we can use random_id, on this case I used random_string. main.tf resource "random_string" "randomz" { length = 8 lower = true special = false upper = false } Above is a resource block where its block label is random_string I defined the block body in that way in order to fit the S3’s requirements. ...

csi interface for eks by terraform

It has been a while since my last post, I was busy these last couples of weeks; meanwhile I’ve learned how to implement a csi interface on eks (aws k8s) and it’s pretty interesting on AWS by EKS service, thus I though it can be useful this content into a post. Requirements: You will need your eks already running. I’ll point each tools, techs, etc I used on this procedure: ...