This page brings together all of our published articles covering modern infrastructure engineering and cloud-native technologies. Each article is rooted in real-world production experience, focusing on practical solutions rather than theoretical concepts.
Infrastructure as Code with Terraform, OpenTofu, and Terragrunt
CI/CD pipelines and automation across GitHub, GitLab, and Azure DevOps
DevOps and GitOps practices with Flux CD and Argo CD
Kubernetes platforms and Linux-based systems
Public and private cloud architectures
Bare-metal and hybrid hosting environments
Cost optimization, operational reliability, and maintainability at scale
The content ranges from deep technical walkthroughs to architecture decisions, implementation patterns, and lessons learned from large production environments.
Every article is guided by the same principles we apply in production:
Lean and efficient design
Automation-first thinking
Cost and operational awareness
Clarity over complexity
Long-term maintainability
Where applicable, we accompany articles with open-source tooling, examples, or reusable components released under the MIT license.
Feel free to scroll through the articles below and explore the ideas, tools, and solutions that shape how we build and operate modern infrastructure.
GitOps Architecture for Bootstrapping Kubernetes Core Services via Flux CD
This article presents an architectural approach for automatically bootstrapping core services in Kubernetes clusters using GitOps principles, with Flux CD as the reconciliation engine. The primary goal is not maximum abstraction or infinite scalability, but a clear, maintainable, and operationally practical foundation that enables a cluster to become usable quickly and remain easy to reason about over time.
The scope of this article is intentionally architecture‑focused. It describes how responsibilities, dependencies, and isolation boundaries are modeled declaratively - across repositories, directories, namespaces, and Flux resources - rather than how to provision infrastructure or tune workloads. Kubernetes itself is assumed to be operational up to the networking layer.
...
Terragrunt CI/CD with Git-Based Filtering
This article presents a CI/CD process for Infrastructure‑as‑Code using Terragrunt with Terraform/OpenTofu. The goal is to enable safe, efficient, and consistent infrastructure changes through a structured workflow. The process is motivated by a few key needs:
allowing multiple developers to work in parallel enforcing segregation‑of‑duty through pull requests and approvals enabling lean deployments by targeting only changed units instead of full stacks maintaining infrastructure consistency between the codebase and the actual infrastructure Such a workflow only works when both the tooling and the team follow the CI/CD principles reliably.
...
A Scalable Terragrunt Repository Architecture for Enterprise Environments
Managing infrastructure with Terraform/OpenTofu and Terragrunt can quickly become complex - especially as environments, teams, and requirements grow. Having a transparent, readable, and DRY (Don’t Repeat Yourself) repository structure is essential for maintaining scalability and manageability over time.
The approach described here has been proven across real-world projects ranging from a few dozen to several hundred Terragrunt units. It’s adaptable to any setup and built around a hierarchical structure that makes it easy to configure, extend, and reuse components.
...
Terragrunt CI/CD with run-all and Provider Caching
As a developer, I’ve spent many hours working with infrastructure-as-code tools, helping automate and manage cloud environments. Over the years, I’ve grown fond of Terraform in combination with Terragrunt. Terragrunt serves as a thin wrapper over Terraform, providing additional functionality to help automate complex workflows and encapsulate Terraform modules.
When working with Terragrunt, it does not take long to find out about the the run-all feature (see: https://terragrunt.gruntwork.io/docs/reference/cli-options/#run-all), which allows me to run multiple Terraform modules in a single call. This functionality for me has proved invaluable in CI/CD pipelines.
...