Alek's Blog - none-technical

ingress-nginx Retirement: Four Ways Forward

aleks — Sat, 18 Jul 2026 00:00:00 +0000

The ingress-nginx</code> Kubernetes controller is not “retiring soon.” It already has. The GitHub repository was archived and made read-only on 2026-03-24, and its own description now reads in the past tense: it was</em> an Ingress controller. For a piece of software that reportedly still runs in front of roughly half of all cloud-native workloads, that is a completed fact, not a countdown.</p>

This is Part 1 of a field guide to migrating away from it. This part is deliberately non-technical — it is for whoever has to decide what to do</em>, not yet for whoever will do the migration work. Parts 2 onward get concrete: inventorying what you actually depend on, an annotation compatibility matrix, migration mechanics, and a reproducible lab.</p>



Sovereign-Cloud-Washing: Five Questions
aleks — Thu, 09 Jul 2026 00:00:00 +0000
“Sovereign cloud” is printed on marketing pages from AWS, Microsoft, Google, and a long list of
European providers alike. The label rarely comes with a definition, which makes it easy to satisfy
on paper and hard to verify in practice. I’ve put together five concrete questions, asked of the
claim itself instead of the label — enough to see, from several angles, what a provider actually
stands behind.</p>


K8s & OpenShift: The Big Picture
aleks — Wed, 01 Jul 2026 00:00:00 +0000
This is the opening post of a seven-part series on Kubernetes and OpenShift best practices, written
from the vantage point of 2026 and eight years of hands-on experience — from initial cluster design
through Day-2 operations and production debugging. This first part is deliberately non-technical: it is about whether</em>
and when</em> a container platform earns its keep — the decisions that happen before anyone writes a
single YAML manifest.</p>


What is a (D)DoS
aleks — Sat, 20 Jun 2026 00:00:00 +0000
(D)DoS attacks are not just a technical problem — they operate at the Business, Social, and Informational level as well. This post covers the non-technical dimensions; the technical follow-up</a> covers Layer 3/4 network floods, BGP hijacking, TLS handshake attacks, Layer 7 application DDoS, and operational resilience.</p>
Originally published at opensourcerers.org</a>; updated with current examples and expanded framing.</p>


How I work with Claude Code
aleks — Wed, 10 Jun 2026 00:00:00 +0000
Since 2025, I have been using AI tools as part of my daily work. Not as a replacement for
thinking — as a productivity aid. An AI coding agent has become a regular part of how I work on infrastructure, blog posts,
and software projects. Most of what follows likely applies to other agents as well —
Cursor, Copilot, or whatever comes next. I happen to use Claude.</p>
This post is not a tutorial and not a pitch. It is a reflection on what actually works — for me, on my projects —
across months of real use, across 40+ projects, and across months of agent use.</p>


LLM Inference on OVH MKS: Introduction
aleks — Tue, 02 Jun 2026 00:00:00 +0000
This post covers the decision context for self-hosting LLM inference on OVH MKS: when it makes sense, what the stack looks like, and what the costs are. Part 2</a> walks through the Terraform and Ansible setup.</p>


AWS vs. GCP vs. Azure vs. OVHcloud: Managed Log Archiving for 7+ Years
aleks — Thu, 14 May 2026 00:00:00 +0000
Long-term log archiving at scale is an expensive problem. Cloud providers offer a wide
range of managed services for ingesting, storing, and querying logs — and the cost
differences between them are dramatic. This series covers AWS, GCP, Azure, and OVH</strong>
along the axes that matter for 7-year archival: services available, storage model, ingest
cost, 7-year total cost at 100 GB/day, Kubernetes integration, security, and query
interfaces.</p>

Full guide:</strong> AWS vs. GCP vs. Azure vs. OVHcloud: The Complete Guide to Managed Log Archiving</a></li>
Part 1 — this post:</strong> Services overview, storage model, and 7-year cost comparison</li>
Part 2 — Pre-Flight, Flexibility & Auditor Export:</a> Pre-flight checklist, retroactive flexibility, auditor export</li>
Part 3 — Operations:</a> Onboarding, Kubernetes integration, ingest pipeline, backup & DR</li>
Part 4 — Security & Compliance:</a> IAM/RBAC, encryption, WORM, GDPR, compliance certificates</li>
Part 5 — Query, Dashboards & Recommendations:</a> Query interfaces, dashboards, alerting, cold-tier behaviour, when to use which</li>
Part 6 — Production Checklist, Guardrails & Runbooks:</a> Loss detection, privacy, schema, cost guardrails, runbooks, fire drills</li>
</ul>
Self-hosted alternative: Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse</a> — tiering, compression, resource consumption, SaaS options.</em></p>

Retaining logs for seven or more years is a very different problem than storing the last
30 days of operational logs. Ingest cost per GB, the ability to query old data without
restoring from tape, and long-term pricing predictability dominate over query latency.
Each of the four providers covered here has a fundamentally different answer to this
problem — and for at least one of them, the honest answer is “our managed offerings are
not designed for this; run it yourself instead.”</p>