# How to Kube Published articles for How to Kube. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kubernetes 1.37 Is Here: Pod Rightsizing, DRA, and Gang Scheduling DevFeed: [Kubernetes 1.37 Is Here: Pod Rightsizing, DRA, and Gang Scheduling]() Original publisher: [Read original article]() Author: Stevie Caldwell Published: 2026-09-08T15:00:00Z Content type: release Language: en Sources: [Fairwinds]() Topics: [Kubernetes](), [scheduling](), [Scalability]() Tags: [cpu](), [how-to-kube](), [kubernetes](), [pod](), [scaling](), [scheduling]() ### AI overview This article reviews Kubernetes 1.37 developments in in-place pod resizing, Dynamic Resource Allocation, and gang scheduling. It explains how pod-level resource management and restart-free resizing are advancing, including requirements and limitations related to cgroup v2. ### Source excerpt Kubernetes 1.37 shipped on August 26, and it's a good time to check in on a couple of features that kept coming up in roadmap conversations: in-place pod resizing and Dynamic Resource Allocation (DRA). Both of these features have been building for several releases now, and 1.37 adds another layer to each. There's also a third one we think is worth watching: gang scheduling through the PodGroup API. It's been alpha since 1.35, and the beta graduation originally planned for 1.36 is now planned for the 1.37 release candidate. ## How We Migrated a Production Cluster from Ingress NGINX to Gateway API DevFeed: [How We Migrated a Production Cluster from Ingress NGINX to Gateway API]() Original publisher: [Read original article]() Author: Husne Ozmen Published: 2026-07-01T17:08:57Z Content type: tutorial Language: en Sources: [Fairwinds]() Topics: [ingress-nginx](), [gateway](), [Kubernetes](), [migration](), [Network](), [Routing (disambiguation)](), [Cross-origin resource sharing (CORS)](), [Firewall](), [service-mesh]() Tags: [cors](), [firewall](), [gateway](), [how-to-kube](), [infrastructure](), [ingress](), [ingress-nginx](), [kubernetes](), [migration](), [production](), [rate-limiting]() ### AI overview A practical account of migrating a production Kubernetes cluster from ingress-nginx to Gateway API under real traffic. It explains Gateway API's resource ownership and typed validation, discusses weighted routing, and describes selecting kgateway based on requirements including CORS, WAF support, and ExternalName replacement. ### Source excerpt Back in January, we published a post about the retirement of ingress-nginx and laid out what that means for teams still running it. We also gave a CNCF CloudNative Live talk a couple of years ago that walked through the case for Gateway API. ## How Do Self-Hosted AI Models Change Your Kubernetes Decisions? DevFeed: [How Do Self-Hosted AI Models Change Your Kubernetes Decisions?]() Original publisher: [Read original article]() Author: Stevie Caldwell Published: 2026-06-24T16:38:35Z Content type: opinion Language: en Sources: [Fairwinds]() Topics: [Kubernetes](), [Artificial Intelligence](), [Self-hosted](), [AI Platform](), [Security](), [software-architecture]() Tags: [ai](), [ai-models](), [artificial-intelligence](), [audit](), [compute](), [cost](), [how-to-kube](), [infrastructure](), [kubernetes](), [self-hosted](), [self-hosted-ai]() ### AI overview The article explains how running AI models in-house changes Kubernetes platform decisions. It compares API-based and self-hosted approaches across cost predictability, GPU and capacity management, operational complexity, and security controls, noting that API-first remains reasonable for sporadic or experimental use. ### Source excerpt Most teams start with API-based AI because it's fast, simple, and easy to ship. You plug an API into your product, pay per request, and don't need to think about infrastructure.