<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4" -->

---
title: Kubernetes: 5 Questions for Graziano Casto — Codemotion...
description: An interview with Graziano Casto, Kubernetes v1.35 Comms Lead and CNCF TAG DevEx Co-Chair, covers In-Place Pod Resize — a feature that lets running pods change...
canonical: https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Kubernetes: 5 Questions for Graziano Casto — Codemotion AI and Tech Conference 2026 | daily.dev
og:description: An interview with Graziano Casto, Kubernetes v1.35 Comms Lead and CNCF TAG DevEx Co-Chair, covers In-Place Pod Resize — a feature that lets running pods change...
og:url: https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4
og:image: https://api.daily.dev/og/posts/WxNqRbHb4.png
og:image:alt: Kubernetes: 5 Questions for Graziano Casto — Codemotion AI and Tech Conference 2026
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Kubernetes: 5 Questions for Graziano Casto — Codemotion AI and Tech Conference 2026

**[Codemotion](https://daily.dev/sources/codemotion)** · 9 min read · 0 upvotes · 0 comments

## Summary

An interview with Graziano Casto, Kubernetes v1.35 Comms Lead and CNCF TAG DevEx Co-Chair, covers In-Place Pod Resize — a feature that lets running pods change CPU/memory requests without a restart. He explains how the old immutable-resource model forced teams to permanently over-provision for startup spikes, wasting cluster capacity and inflating cloud bills. He discusses how the feature mainly benefits platform teams building smarter internal tooling, why conference talks help close the awareness gap between shipped KEPs and actual developer usage, and what's still missing: HPA and VPA don't coordinate on scaling decisions, and while PSI (pressure stall information) metrics became stable in Kubernetes 1.36, built-in autoscalers don't yet natively use that signal.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.codemotion.com/magazine/devops/cloud/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026>

## Questions this post answers

### What is Kubernetes In-Place Pod Resize and why does it matter for cloud costs?

In-Place Pod Resize lets a running Kubernetes pod change its CPU or memory requests and limits without being restarted, something previously impossible because resource values were treated as immutable once a pod started. Before this, teams set requests at worst-case startup levels (e.g., four CPUs) permanently, wasting capacity since steady-state usage might be a fraction of that, inflating node counts and cloud bills. With in-place resize, requests can burst up temporarily then scale back down automatically, cutting node count and spend without code changes.

_Teams sizing Kubernetes clusters can follow feature rollouts like this one on daily.dev to catch real cost-saving levers early._

### Is pressure stall information (PSI) stable in Kubernetes and can autoscalers use it yet?

As of Kubernetes 1.36, PSI metrics are stable and exposed by the kubelet, solving the data availability problem. However, the built-in Horizontal Pod Autoscaler (HPA) and Vertical Pod Autoscaler (VPA) that most clusters actually run do not yet natively consume that signal. Today only custom controllers pull PSI in on their own, so most scaling decisions still rely on a partially complete picture of application resource pressure.

_Anyone tuning Kubernetes autoscaling can track when HPA and VPA add native PSI support via daily.dev._

### Why don't HPA and VPA coordinate when scaling Kubernetes pods?

Horizontal Pod Autoscaler (HPA) decides replica count and Vertical Pod Autoscaler (VPA) decides per-pod size, but the two act independently rather than coordinating, so both can fire on the same spike and scale out and up simultaneously when either alone would have sufficed. Early work is underway toward a more multidimensional scheduler that reasons about both axes together instead of two controllers reacting separately to the same signal.

_Engineers weighing HPA versus VPA tradeoffs can follow this coordination work as it develops on daily.dev._

## Similar posts on daily.dev

- [The Efficiency Era: How Kubernetes v1.35 Finally Solves the “Restart” Headache](https://daily.dev/posts/the-efficiency-era-how-kubernetes-v1-35-finally-solves-the-restart-headache-fjhms6zq4) · Cloud Native Now · 22 upvotes · 0 comments
- [Why Kubernetes 1.35 is a game-changer for stateful workload scaling](https://daily.dev/posts/why-kubernetes-1-35-is-a-game-changer-for-stateful-workload-scaling-h3xwtunre) · The New Stack · 1 upvotes · 0 comments
- [Best Pod Rightsizing Tools for Kubernetes](https://daily.dev/posts/best-pod-rightsizing-tools-for-kubernetes-zh2efcfme) · Cast AI · 0 upvotes · 0 comments

---

Tags: [#devtools](https://daily.dev/tags/devtools), [#kubernetes](https://daily.dev/tags/kubernetes), [#finops](https://daily.dev/tags/finops)

[View this post on daily.dev](https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Kubernetes: 5 Questions for Graziano Casto — Codemotion AI and Tech Conference 2026","url":"https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4"},"datePublished":"2026-09-08T19:10:57.997Z","dateModified":"2026-09-13T21:37:45.962Z","description":"An interview with Graziano Casto, Kubernetes v1.35 Comms Lead and CNCF TAG DevEx Co-Chair, covers In-Place Pod Resize — a feature that lets running pods change...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2fb61c0b459b28b6f21d3a0eaefe9ee3?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2fb61c0b459b28b6f21d3a0eaefe9ee3?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Codemotion","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Codemotion","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/008c4c0fe1ba4cd3b6a6740d442d242b","url":"https://daily.dev/sources/codemotion"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devtools,kubernetes,finops","timeRequired":"PT9M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Codemotion","item":"https://daily.dev/sources/codemotion"},{"@type":"ListItem","position":3,"name":"Kubernetes: 5 Questions for Graziano Casto — Codemotion AI and Tech Conference 2026"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/kubernetes-5-questions-for-graziano-casto-codemotion-ai-and-tech-conference-2026-wxnqrbhb4#faq","mainEntity":[{"@type":"Question","name":"What is Kubernetes In-Place Pod Resize and why does it matter for cloud costs?","acceptedAnswer":{"@type":"Answer","text":"In-Place Pod Resize lets a running Kubernetes pod change its CPU or memory requests and limits without being restarted, something previously impossible because resource values were treated as immutable once a pod started. Before this, teams set requests at worst-case startup levels (e.g., four CPUs) permanently, wasting capacity since steady-state usage might be a fraction of that, inflating node counts and cloud bills. With in-place resize, requests can burst up temporarily then scale back down automatically, cutting node count and spend without code changes. Teams sizing Kubernetes clusters can follow feature rollouts like this one on daily.dev to catch real cost-saving levers early."}},{"@type":"Question","name":"Is pressure stall information (PSI) stable in Kubernetes and can autoscalers use it yet?","acceptedAnswer":{"@type":"Answer","text":"As of Kubernetes 1.36, PSI metrics are stable and exposed by the kubelet, solving the data availability problem. However, the built-in Horizontal Pod Autoscaler (HPA) and Vertical Pod Autoscaler (VPA) that most clusters actually run do not yet natively consume that signal. Today only custom controllers pull PSI in on their own, so most scaling decisions still rely on a partially complete picture of application resource pressure. Anyone tuning Kubernetes autoscaling can track when HPA and VPA add native PSI support via daily.dev."}},{"@type":"Question","name":"Why don't HPA and VPA coordinate when scaling Kubernetes pods?","acceptedAnswer":{"@type":"Answer","text":"Horizontal Pod Autoscaler (HPA) decides replica count and Vertical Pod Autoscaler (VPA) decides per-pod size, but the two act independently rather than coordinating, so both can fire on the same spike and scale out and up simultaneously when either alone would have sufficed. Early work is underway toward a more multidimensional scheduler that reasons about both axes together instead of two controllers reacting separately to the same signal. Engineers weighing HPA versus VPA tradeoffs can follow this coordination work as it develops on daily.dev."}}]}
```

