<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reliability on GeekyRyan</title><link>https://rnemeth90.github.io/tags/reliability/</link><description>Recent content in Reliability on GeekyRyan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Mar 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://rnemeth90.github.io/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>Diagnosing and Safely Re-enabling AKS Automatic Node Image Updates</title><link>https://rnemeth90.github.io/projects/2023-03-21-aks-automatic-node-image-updates/</link><pubDate>Tue, 21 Mar 2023 09:00:00 +0000</pubDate><guid>https://rnemeth90.github.io/projects/2023-03-21-aks-automatic-node-image-updates/</guid><description>&lt;p&gt;AKS has a feature that automatically applies the latest node image to your node pools on a schedule. It&amp;rsquo;s a great way to stay current on OS-level patches without manual intervention - until it causes a service degradation in prod.&lt;/p&gt;&#10;&lt;p&gt;After an automatic node image rollout caused instability in one of our environments, we disabled the feature while we investigated with Microsoft support. No definitive root cause was found, but the support engagement did produce some useful recommendations around additional node-level logging to capture if the issue recurred.&lt;/p&gt;</description></item></channel></rss>