<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Troubleshooting on vsz@ | Kubernetes, AI, tech stuff</title><link>https://victorszalvay.com/tags/troubleshooting/</link><description>Recent content in Troubleshooting on vsz@ | Kubernetes, AI, tech stuff</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Victor Szalvay — All rights reserved</copyright><lastBuildDate>Mon, 21 Sep 2026 09:00:00 -0700</lastBuildDate><atom:link href="https://victorszalvay.com/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>ComputeClass observability: which priority rule provisioned this node?</title><link>https://victorszalvay.com/computeclass-observability/</link><pubDate>Mon, 21 Sep 2026 09:00:00 -0700</pubDate><guid>https://victorszalvay.com/computeclass-observability/</guid><description>&lt;p&gt;&lt;em&gt;GKE 1.36.4 gives ComputeClasses a real status surface: per-priority conditions with
backoff timers, a node annotation that names the priority rule that provisioned it, and an
audit-log trail that outlives the nodes themselves. This has been the longest-standing gap in
the API, and it&amp;rsquo;s worth an afternoon of your time to get functional with it.&lt;/em&gt;&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://victorszalvay.com/computeclass-observability/cover.png"/></item></channel></rss>