MisLinux is an independent technical blog by Vicente Arteaga Gómez. It documents the real-world process of designing, deploying, and operating small Kubernetes clusters on Hetzner Cloud for production workloads.
Who writes this
My name is Vicente Arteaga Gómez. I work in fintech/ad-tech infrastructure and have been running production systems on Linux for over three decades. Most of my daily work involves Kubernetes cluster operations, container image pipelines, multi-architecture builds, bare-metal and cloud-native networking, and building the kind of tooling that makes a small team able to operate infrastructure that a larger team would normally need.
The infrastructure I operate includes:
- A multi-node Kubernetes cluster on Hetzner Cloud (ARM64 + AMD64 mixed node pool)
- Private container registry with multi-arch image publishing
- Automated monitoring with Prometheus, Grafana, and alert routing to Telegram
- Real-time VAST ad-server workloads handling production traffic
- CI/CD pipelines driven by Gerrit and custom PHP build tooling
- Hetzner-managed DNS, Cloudflare CDN integration, cert-manager, and external-dns automation
I am based in Spain. I have worked across the full stack from PHP and Rust application code to Kubernetes manifests, Terraform provisioning, and Linux kernel-level networking.
What this blog is for
The goal is simple: publish practical notes that help operators avoid the expensive mistakes that usually appear after the first successful deployment. That includes cluster bootstrapping, networking, firewalls, ingress, TLS, storage, upgrades, backups, and the operational tradeoffs that only become obvious after a cluster has been running for a while.
What you can expect here:
- first-person experience from real production workloads, not lab exercises
- honest tradeoffs, including what did not work and why
- cost-aware infrastructure choices with real numbers
- decision rules and checklists that survive under operational pressure
- original terminal output, architecture notes, cost tables, and incident timelines
Most articles grow out of something I actually debugged, refactored, or rebuilt. If something went wrong before it went right, I say so.
Independence statement
This is an independent technical publication. I am not affiliated with, sponsored by, or endorsed by Hetzner, Google, Docker, Kubernetes, or any other vendor or product mentioned on this site. The current monetization plan is limited to advertising such as Google AdSense. If sponsored content, affiliate relationships, or paid product placements are ever added, they will be clearly disclosed in the relevant articles.
Contact
For questions, corrections, or suggestions: mislinuxtech@gmail.com
If you run Kubernetes on Hetzner, or are planning to, this blog is for you.
