RSS NOC Intelligence

<p>The Kubernetes project relies on transparency to empower cluster administrators and security researchers. One important way we do that is by publishing CVE records into the Common Vulnerabilities and Exposures database. As part of our ongoing effort to mature the official <a href="https://kubernetes.io/docs/reference/issues-security/official-cve-feed/index.json">Kubernetes CVE Feed</a>, we have identified some dis

<p>After several years of development, User Namespaces support in Kubernetes reached General Availability (GA) with the v1.36 release. This is a Linux-only feature.</p> <p>For those of us working on low level container runtimes and rootless technologies, this has been a long awaited milestone. We finally reached the point where &quot;rootless&quot; security isolation can be used for Kubernetes workloads.</p> <p>This

<p>On behalf of Kubernetes SIG Auth and SIG Node, we are pleased to announce the graduation of fine-grained <code>kubelet</code> API authorization to General Availability (GA) in Kubernetes v1.36!</p> <p>The <code>KubeletFineGrainedAuthz</code> feature gate was introduced as an opt-in alpha feature in Kubernetes v1.32, then graduated to beta (enabled by default) in v1.33. Now, the feature is generally available and t

<p>Kubernetes v1.36 introduces <a href="https://kubernetes.io/docs/concepts/workloads/resource-managers/#pod-level-resource-managers">Pod-Level Resource Managers</a> as an alpha feature, bringing a more flexible and powerful resource management model to performance-sensitive workloads. This enhancement extends the kubelet's Topology, CPU, and Memory Managers to support pod-level resource specifications (<code>.spec.r

<p>If you've ever tried to enforce a security policy across a fleet of Kubernetes clusters, you've probably run into a frustrating chicken-and-egg problem. Your admission policies are API objects, which means they don't exist until someone creates them, and they can be deleted by anyone with the right permissions. There's always a window during cluster bootstrap where your policies aren't active yet, and there's no w

<p>Dynamic Resource Allocation (DRA) has fundamentally changed how platform administrators handle hardware accelerators and specialized resources in Kubernetes. In the v1.36 release, DRA continues to mature, bringing a wave of feature graduations, critical usability improvements, and new capabilities that extend the flexibility of DRA to native resources like memory and CPU, and support for ResourceClaims in PodGroup

<p>The <code>.spec.externalIPs</code> field for <a href="https://kubernetes.io/docs/concepts/services-networking/service/">Service</a> was an early attempt to provide cloud-load-balancer-like functionality for non-cloud clusters. Unfortunately, the API assumes that every user in the cluster is fully trusted, and in any situation where that is not the case, it enables various security exploits, as described in <a href

<p>Back in Kubernetes 1.28, we introduced the <code>Mixed Version Proxy (MVP)</code> as an Alpha feature (under the feature gate <code>UnknownVersionInteroperabilityProxy</code>) in a <a href="https://kubernetes.io/blog/2023/08/28/kubernetes-1-28-feature-mixed-version-proxy-alpha/">previous blog post</a>. The goal was simple but critical: make cluster upgrades safer by ensuring that requests for resources not yet kno

<p>Since its original implementation in the Linux kernel in 2018, <em>Pressure Stall Information</em> (PSI) has provided users with the high-fidelity signals needed to identify resource saturation before it becomes an outage. Unlike traditional utilization metrics, PSI tells the story of tasks stalled and time lost, all in nicely-packaged percentages of time across the CPU, memory, and I/O.</p> <p>With the recent rel

<p>The rising popularity of AI, Edge, and Telecommunications workloads on Kubernetes has led to new requirements for hardware management. We now need hardware specification beyond CPU time and memory allocations. This includes allocating GPUs, TPUs, network interfaces, and other hardware, sometimes after pod start and occasionally through time-sharing.</p> <p>Efficiently managing this specialized hardware is the miss

<p>The landscape of artificial intelligence is undergoing a massive architectural shift. In the early days of generative AI, interacting with a model was often treated as a transient, stateless function call: a request that spun up, executed for perhaps 50 milliseconds, and terminated.</p> <p>Today, the world is witnessing AI v2 eating AI v1. The ecosystem is moving from short-lived, isolated tasks to deploying multi

<img alt="Logo for node readiness controller" src="https://kubernetes.io/node-readiness-controller-logo.svg" style="float: right; display: inline-block; margin-left: 2em;" /> <p>In the standard Kubernetes model, a node’s suitability for workloads hinges on a single binary &quot;Ready&quot; condition. However, in modern Kubernetes environments, nodes require complex infrastructure dependencies—such as network agents,

<p>The community around Kubernetes includes a number of Special Interest Groups (SIGs) and Working Groups (WGs) facilitating discussions on important topics between interested contributors. Today, we're excited to announce the formation of the <a href="https://github.com/kubernetes-sigs/wg-ai-gateway">AI Gateway Working Group</a>, a new initiative focused on developing standards and best practices for networking infr

<p>During production debugging, the fastest route is often broad access such as <code>cluster-admin</code> (a ClusterRole that grants administrator-level access), shared bastions/jump boxes, or long-lived SSH keys. It works in the moment, but it comes with two common problems: auditing becomes difficult, and temporary exceptions have a way of becoming routine.</p> <p>This post offers my recommendations for good pract

<p>With the Ingress-NGINX <a href="https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/">retirement</a> scheduled for March 2026, the Kubernetes networking landscape is at a turning point. For most organizations, the question isn't whether to migrate to <a href="https://gateway-api.sigs.k8s.io/">Gateway API</a>, but how to do so safely.</p> <p>Migrating from Ingress to Gateway API is a fundamental shift in

<p>Kubernetes v1.36 promotes the ability to modify container resource requests and limits in the pod template of a suspended Job to beta. First introduced as alpha in v1.35, this feature allows queue controllers and cluster administrators to adjust CPU, memory, GPU, and extended resource specifications on a Job while it is suspended, before it starts or resumes running.</p> <h2 id="why-mutable-pod-resources-for-suspe

<p>Following the graduation of Pod-Level Resources to Beta in v1.34 and the General Availability (GA) of In-Place Pod Vertical Scaling in v1.35, the Kubernetes community is thrilled to announce that <strong>In-Place Pod-Level Resources Vertical Scaling has graduated to Beta in v1.36!</strong></p> <p>This feature is now enabled by default via the <code>InPlacePodLevelResourcesVerticalScaling</code> feature gate. It al

<p>In Kubernetes v1.36, <strong>Declarative Validation</strong> for Kubernetes native types has reached General Availability (GA).</p> <p>For users, this means more reliable, predictable, and better-documented APIs. By moving to a declarative model, the project also unlocks the future ability to publish validation rules via OpenAPI and integrate with ecosystem tools like Kubebuilder. For contributors and ecosystem de

<p>As Kubernetes clusters grow to tens of thousands of nodes, controllers that watch high-cardinality resources like Pods face a scaling wall. Every replica of a horizontally scaled controller receives the full stream of events from the API server, paying the CPU, memory, and network cost to deserialize everything, only to discard the objects it is not responsible for. Scaling out the controller does not reduce per-r

<p>AI/ML and batch workloads introduce unique scheduling challenges that go beyond simple Pod-by-Pod scheduling. In Kubernetes v1.35, we introduced the first tranche of <em>workload-aware scheduling</em> improvements, featuring the foundational Workload API alongside basic <em>gang scheduling</em> support built on a Pod-based framework, and an <em>opportunistic batching</em> feature to efficiently process identical P

<p>SIG-Etcd announces the availability of the <a href="https://github.com/etcd-io/etcd/releases/tag/v3.7.0-beta.0">first beta release of etcd v3.7.0</a>. This new version of the popular distributed database and key Kubernetes component includes the long-requested RangeStream feature, as well as a refactoring and cleanup of multiple legacy components and interfaces. v3.7 will deliver improved security, better operatio

<p>For many people, Kubernetes Dashboard was their first window into Kubernetes. It offered a simple visual way to see what was running in a cluster, inspect resources, and build confidence without relying on the command line. For years, it helped developers, students, and operators make sense of Kubernetes, and it served as an important onramp into the ecosystem.</p> <p>The Kubernetes Dashboard project has now been

<p><a href="https://headlamp.dev/">Headlamp</a> is an open-source, extensible Kubernetes SIG UI project designed to let you explore, manage, and debug cluster resources.</p> <p><a href="https://knative.dev/">Knative</a> brings serverless workloads to Kubernetes, handling traffic routing, autoscaling, and revision management so teams can deploy and iterate without fighting infrastructure. But operating Knative workloa

<p><a href="https://volcano.sh/">Volcano</a> is a cloud native batch scheduler for Kubernetes, built for high-performance computing, AI/ML, and other batch workloads.</p> <p><a href="https://headlamp.dev/">Headlamp</a> is an extensible Kubernetes web UI. With its plugin system, Headlamp can surface APIs and workflows beyond the built-in Kubernetes resources. The Volcano plugin brings core Volcano resources into Headl

<p><a href="https://headlamp.dev/">Headlamp</a> is an open-source, extensible Kubernetes SIG UI project designed to let you explore, manage, and debug cluster resources directly from a browser.</p> <p><a href="https://cluster-api.sigs.k8s.io">Cluster API (CAPI)</a> is a Kubernetes sub-project that brings declarative, Kubernetes-style APIs to cluster lifecycle management. It lets platform teams provision, upgrade, and

<p>AI has really changed the game around software development. More people are leveraging AI than ever to contribute patches to projects they use. To me, this is a good thing as more folks will contribute patches rather than fork or not fix them. The main problem is that AI has made generating code fast but there has been very little improvement in maintaining code bases. In this post, we will highlight the ways the

<p><em>This article is a mirror of the <a href="https://etcd.io/blog/2026/announcing-etcd-3.7/">original announcement</a></em></p> <p>Today, SIG etcd is releasing <a href="https://github.com/etcd-io/etcd/releases/tag/v3.7.0">etcd v3.7.0</a>, the latest minor release of the popular distributed key-value store and core Kubernetes component. v3.7 ships the long-requested RangeStream feature, delivers several other perfo

<h2 id="1-before-you-start-know-what-is-changing">1. Before you start: know what is changing<a class="td-heading-self-link" href="https://kubernetes.io/feed.xml#1-before-you-start-know-what-is-changing"></a></h2><p>Kubernetes Dashboard and Headlamp both show what is running in a cluster, but they work differently. When Headlamp runs on the desktop, it uses your existing kubeconfig to connect to one or more clusters a

<p>Kubernetes has quietly become the default platform for AI and machine learning. Whether you run notebook servers for data scientists, schedule distributed training jobs, tune hyperparameters, or orchestrate multi-step ML pipelines, those workloads increasingly land on a Kubernetes cluster. <a href="https://www.kubeflow.org/">Kubeflow</a> is one of the most popular ways to assemble that stack, and it does so the Ku

<p>Kubernetes ships with built-in awareness of CPU and memory, but most real-world scaling decisions depend on signals that live entirely outside that narrow window: how many messages are waiting in a queue, how long the last batch job took, how many active WebSocket connections a pod is holding. When the built-in metrics are not enough, a <em>metrics exporter</em> bridges that gap.</p> <p>This post walks through wri

<p>As we get closer to the release date for Kubernetes v1.37, the project develops and matures, features may be deprecated, removed, or replaced with better ones for the project's overall health. This blog outlines some of the planned changes for the Kubernetes v1.37 release that the release team feels you should be aware of for the continued maintenance of your Kubernetes environment and keeping up to date with the

<p><img alt="Gateway API logo" src="https://kubernetes.io/blog/2026/08/03/gateway-api-v1-6-release/gateway-api-logo.svg" /></p> <p>The Kubernetes SIG Network community is thrilled to share the release of <strong>Gateway API v1.6.0</strong>, which was released on June 30th of this year!</p> <p>Gateway API has become the standard for modern, role-oriented, and expressive service networking in Kubernetes. In previous re

<p>YAML has been the standard way to write Kubernetes manifests for years. Every example, tutorial, and configuration file you come across is written in it. The problem isn't that YAML is a bad format. It's that YAML gives you a lot of choices, and not all of them are equally good for writing Kubernetes manifests. Some features make files harder to read, some are easy to misuse and others can lead to surprising behav

<p><strong>In March 2026, Kubernetes will retire Ingress NGINX, a piece of critical infrastructure for about half of cloud native environments.</strong> The retirement of Ingress NGINX was <a href="https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/">announced</a> for March 2026, after years of <a href="https://groups.google.com/a/kubernetes.io/g/dev/c/rxtrKvT_Q8E/m/6_ej0c1ZBAAJ">public warnings</a> that

<p>I'm excited to announce the implementation of an improved conversion formula from cgroup v1 CPU shares to cgroup v2 CPU weight. This enhancement addresses critical issues with CPU priority allocation for Kubernetes workloads when running on systems with cgroup v2.</p> <h2 id="background">Background<a class="td-heading-self-link" href="https://kubernetes.io/feed.xml#background"></a></h2><p>Kubernetes was originally