<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nginx on GeekyRyan</title><link>https://rnemeth90.github.io/tags/nginx/</link><description>Recent content in Nginx on GeekyRyan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 14 May 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://rnemeth90.github.io/tags/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>Emergency Patching of Nginx VM Scale Sets and Kubernetes Nodes for a Critical CVE</title><link>https://rnemeth90.github.io/projects/2026-05-14-patching-nginx-for-a-critical-cve/</link><pubDate>Thu, 14 May 2026 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2026-05-14-patching-nginx-for-a-critical-cve/</guid><description>&lt;p&gt;Critical CVE in Linux copy_file_range hit both Nginx VMs and AKS Linux nodes. Multiple scale sets, multiple clusters, spanning production, RC, test, and lab. Need to patch everything in the blast radius.&lt;/p&gt;&#10;&lt;p&gt;Production gets the formal process - change request, off-hours patching to minimize maintenance window impact. Lab and test can move faster. Scope was big, but having a clear map of what&amp;rsquo;s affected and what process each environment needs let us move fast where we could and be deliberate where it mattered.&lt;/p&gt;</description></item><item><title>Upgrading Nginx Across the Environment</title><link>https://rnemeth90.github.io/projects/2025-03-20-nginx-version-upgrade/</link><pubDate>Thu, 20 Mar 2025 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2025-03-20-nginx-version-upgrade/</guid><description>&lt;p&gt;Nginx upgrade across the board - one of those quiet maintenance projects that keeps you off end-of-life versions and away from CVEs. Nothing flashy, but necessary.&lt;/p&gt;&#10;&lt;p&gt;The interesting part was that Nginx licensing has shifted around over the years for different distributions and modules, so before pushing the upgrade out I had to sort out which license terms applied to what we were running. It&amp;rsquo;s a good reminder that even straightforward upgrade projects sometimes have compliance homework hiding inside them.&lt;/p&gt;</description></item></channel></rss>