<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cluster Autoscaler on vsz@ | Kubernetes, AI, tech stuff</title><link>https://victorszalvay.com/tags/cluster-autoscaler/</link><description>Recent content in Cluster Autoscaler on vsz@ | Kubernetes, AI, tech stuff</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Victor Szalvay — All rights reserved</copyright><lastBuildDate>Mon, 17 Aug 2026 09:00:00 -0700</lastBuildDate><atom:link href="https://victorszalvay.com/tags/cluster-autoscaler/index.xml" rel="self" type="application/rss+xml"/><item><title>CapacityQuota: limiting what the autoscaler provisions, not what pods request</title><link>https://victorszalvay.com/capacityquota-granular-scale-up-limits/</link><pubDate>Mon, 17 Aug 2026 09:00:00 -0700</pubDate><guid>https://victorszalvay.com/capacityquota-granular-scale-up-limits/</guid><description>&lt;p&gt;&lt;em&gt;A new cluster-scoped CRD lets you cap autoscaling by node attribute — machine family,
accelerator type, zone, ComputeClass — rather than by namespace. It closes a gap
&lt;code&gt;ResourceQuota&lt;/code&gt; was never shaped to fill, and it lands upstream in
&lt;code&gt;kubernetes/autoscaler&lt;/code&gt;, not only in GKE.&lt;/em&gt;&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://victorszalvay.com/capacityquota-granular-scale-up-limits/cover.png"/></item></channel></rss>