I

infrastructure-as-code

Collection of configuration files used to deploy and manage my little "cloud" of self-hosted services.

Everything is automated using GitLab CI/CD.

Infrastructure-as-code project for my self-hosting hobby and more.

Homelab infrastructure as code - Proxmox, Docker (dockhost), Kubernetes (kubecluster)

Terraform on AWS: modular VPC + EC2, EKS with registry modules, and a Jenkins pipeline that provisions, deploys and destroys its own infrastructure. S3 remote state, GitLab CI (fmt, tflint, validate), and documented real-world troubleshooting.

Production-grade Multi-Cloud Kubernetes & IaC Platform across AWS & Azure. Features Terraform, EKS, AKS, Helm, S3 Glacier DR, and Zero-Trust Network Security.

What Terraform describes in GCP for LedgerFlow — modules, one environment, nothing applied by hand

Production style AWS platform built as code with multi-account organization, least-privilege GitLab OIDC pipelines, hardened state storage, tested security controls.

Production-style DevSecOps platform on AWS: STIG-hardened RKE2 Kubernetes on RHEL 9, built from code with Terraform, Ansible and Puppet. GitLab CI scan gates, Harbor, GitOps with Argo CD, Keycloak SSO and air-gapped delivery. One command builds it, one tears it down.

OpenTofu/Terraform module for managing Rancher system-upgrade-controller and pinned K3s or RKE2 upgrade plans

OpenTofu/Terraform module for granting an automation agent a scoped ServiceAccount (cluster-wide read + targeted write) and a minted kubeconfig in a Kubernetes cluster

OpenTofu/Terraform module for managing GitLab projects — branch protection, tag protection, badges, variables

Serie práctica de infraestructura empresarial en Linux: 10 laboratorios de Infraestructura como Código (IaC) con OpenTofu, CentOS Stream 10, SELinux en modo Enforcing y estándares FHS 3.0 para r/LinuxEnEspanol patrocinada por Cherry Servers.

tf-infra — Live Terraform Infrastructure

Provisions and manages the homelab private cloud using reusable modules from tf-modules.

Live Terraform configurations that compose modules from tf-modules to provision actual infrastructure. Each environment is an independent root module with its own state.

Environments production: NAT network 10.0.100.0/24, DHCP, local DNS via libvirt staging: NAT network 10.0.101.0/24, separate domain (staging.homelab.local) What's in here environments/production/: Production root module — network layer, state, tfvars environments/staging/: Staging root module — mirrors production with isolated state CI/CD: terraform fmt + terraform validate for all environments, AI code review, semver auto-tagging Tech Stack IaC: Terraform (managed via tfenv) Provider: libvirt Modules: Sourced from yggdrasil13/hnoss/tf-modules via git SSH + semver tag

Medium-interaction SSH/Telnet honeypot built with Cowrie, Loki, Promtail, and Grafana - provisioned on DigitalOcean via Terraform with a GitLab CI validation pipeline.

Infrastructure as code for ruslangaiderbek.dev: Terraform for three Cloudflare zones and the Vercel projects, a dormant Hetzner + Ansible contour, state kept in GitLab.

Repo for homelab infrastructure code, hosted on Proxmox CE, resources provisioned via Terraform + Ansible.

My GitHub account configuration (https://github.com/ginolatorilla)

Fish skeleton - infrastructure template: Terraform (Hetzner + Cloudflare, GitLab-managed state), Ansible skeleton, Cloudflare-only firewall, SSL/DNS canon

Provisions the demonstration's infrastructure with Terraform, planned and applied against a GitLab-managed state backend.