Technical blogs rarely need a paywall. A clear, optional support CTA is enough. DevOpsTales uses a per-post coffeebox partial plus a floating Buy Me a Coffee widget in the footer so readers can tip without leaving the page chrome.

Disqus-style comment SaaS is heavy for a static blog. Utterances stores each discussion as a GitHub Issue, loads a small client script, and authenticates with GitHub. DevOpsTales wires it through a partial and a per-post disable_comments flag.

RSS and Atom are still how a lot of readers and tools discover new posts. Hugo can emit both from the same content tree. On DevOpsTales the site ships classic RSS plus Atom via the hugo-atom-feed component theme, with a custom Atom template that skips the filedir partial section.

HTML is fine for humans in a browser. For AI agents it is often a pile of navigation, scripts, sidebars, and chrome wrapped around the few paragraphs that actually matter. If you run a technical Hugo site, you can serve a clean text sibling of every post plus a site-wide llms.txt index so agents skip the HTML tax.

AI is transforming DevOps practices through agentic AI systems that go beyond simple chatbots. These coding agents combine large language models with tools, memory, and planning capabilities to autonomously handle complex Platform Engineering and SRE tasks. By integrating with MCPs (Model Context Protocol), skills, and spec-driven development workflows, agents can create observability systems, build infrastructure APIs, and manage systems with minimal human intervention.

If you have been doing DevOps long enough, you remember the shift from artisanal deploys to pipeline-as-code. The next shift will feel familiar in shape even if the ingredients look alien: we are still wiring stages, gates, and blast radius—but some stages will call models and tools, not only make and kubectl.

Implementing group-based authorization at the ingress level ensures that sensitive applications are only accessible to authorized user groups. This post covers implementing zero-trust ingress with Traefik + Authorino where different ingress routes are only visible to specific user groups.

This final post brings together everything from the egress gateway series with a comprehensive comparison of all 8 solutions, decision matrices for different scenarios, cost analysis, and practical migration strategies.

Cloud providers offer managed NAT services that provide egress control for Kubernetes clusters without the operational overhead of self-managed solutions. This post covers native cloud NAT options from AWS, GCP, and Azure with practical configuration examples.

Squid is a mature, full-featured HTTP proxy and caching server that can be deployed on Kubernetes for egress control. This post explores using traditional proxy technology for modern Kubernetes egress requirements with access control, caching, and comprehensive logging.