# Kubernetes Open source platform for automating deployment, scaling, and management of containerized applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Introducing Amazon SageMaker HyperPod Inference Gateway DevFeed: [Introducing Amazon SageMaker HyperPod Inference Gateway]() Original publisher: [Read original article]() Author: Vinay Arora Published: 2026-09-18T13:08:34Z Content type: release Language: en Sources: [Artificial Intelligence]() Topics: [Amazon SageMaker HyperPod](), [Model Routing](), [model-serving](), [Inference Performance](), [Amazon Elastic Kubernetes Service](), [Kubernetes](), [AI Inference](), [GPU](), [AI Platform](), [Prometheus]() Tags: [amazon-eks](), [amazon-sagemaker-hyperpod](), [announcements](), [expert-400](), [gpu](), [inference](), [kubernetes](), [latency](), [metrics](), [model-serving](), [performance](), [routing]() ### AI overview Amazon SageMaker HyperPod Inference Gateway is a Kubernetes-native, GPU-aware routing add-on for Amazon EKS. It uses real-time GPU signals and model-serving metrics to route inference requests to suitable pods, aiming to reduce GPU waste and first-token latency without application changes. ### Source excerpt Amazon SageMaker HyperPod Inference Gateway is a Kubernetes-native, GPU-aware routing add-on for Amazon EKS. It uses real-time GPU signals to send each inference request to the best-suited pod, cutting first-token latency by up to 82% with no changes to your model servers or client applications. ## WSO2 Releases Agent Manager as Enterprises Look to Control Growing AI Agent Sprawl DevFeed: [WSO2 Releases Agent Manager as Enterprises Look to Control Growing AI Agent Sprawl]() Original publisher: [Read original article]() Author: Craig Risi Published: 2026-09-18T12:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [AI Agent](), [Artificial Intelligence](), [Authorization](), [Security](), [Deployment](), [Kubernetes](), [Model Context Protocol](), [OpenTelemetry]() Tags: [agent-identity](), [agentic-ai-architecture](), [ai](), [ai-agent](), [ai-agents](), [ai-development](), [ai-ml-data-engineering](), [aiops](), [authorization](), [deployment](), [devops](), [governance](), [kubernetes](), [ml-data-engineering](), [model-context-protocol](), [news](), [opentelemetry](), [ws02-agent-manager](), [ws02-stratos]() ### AI overview WSO2 has released Agent Manager, an open-source platform for governing AI agents across models, frameworks, and deployment environments. The general availability release adds agent identity and authorization, MCP governance, lifecycle controls, a Kubernetes-native sandboxed runtime, and OpenTelemetry-based tracing and evaluation. ### Source excerpt WSO2 has announced the general availability of WSO2 Agent Manager, an open-source platform designed to provide centralized governance, identity management, security controls, and operational oversight for AI agents running across different models, frameworks, and deployment environments. By Craig Risi ## Week Ending September 13, 2026 DevFeed: [Week Ending September 13, 2026]() Original publisher: [Read original article]() Published: 2026-09-18T06:22:00Z Content type: news Language: en Sources: [Last Week in Kubernetes Development]() Topics: [Kubernetes](), [releases](), [SDKs](), [Go Language](), [Post-Quantum](), [Security](), [TypeScript](), [configuration](), [Python]() Tags: [configuration](), [developer](), [go](), [instrumentation](), [kubernetes](), [news](), [post-quantum](), [release](), [sdks](), [security]() ### AI overview Developer News summarizes Kubernetes project updates for the week ending September 13, 2026, including kubelet static-binary discussions, SIG leadership and subprojects, AI Conformance changes, Agent Sandbox v1.0, the Kubernetes v1.38 release cycle, memory-management configuration, and post-quantum certificate support. ### Source excerpt Developer News ## How Equinix cut operational overhead with a shared services architecture on Amazon EKS DevFeed: [How Equinix cut operational overhead with a shared services architecture on Amazon EKS]() Original publisher: [Read original article]() Author: Chhavi Kaushik Published: 2026-09-17T18:00:56Z Content type: article Language: en Sources: [AWS Architecture Blog]() Topics: [Amazon EKS](), [Kubernetes](), [Architecture & Design](), [Cloud](), [Deployment](), [Provisioning](), [observability](), [Security](), [CI/CD](), [Open Source]() Tags: [amazon-eks](), [amazon-elastic-kubernetes-service](), [architecture](), [customer-solutions](), [deployment](), [infrastructure](), [kubernetes](), [observability](), [pipelines](), [provisioning](), [security]() ### AI overview Equinix moved from independently managed Kubernetes clusters on Amazon EC2 to a shared services architecture on Amazon EKS. The approach centralizes governance and common infrastructure services while addressing operational sprawl, lifecycle complexity, security, networking, observability, and deployment consistency. ### Source excerpt Equinix, the world's digital infrastructure company, built a shared services architecture on Amazon EKS to eliminate the operational sprawl of its self-managed Kubernetes environment. Learn how a multi-account North Star architecture centralized governance and shared services, delivering 4x faster deployments and 40% less operational overhead. ## От Kubernetes-платформы к управлению гибридной распределённой инфраструктурой: встречайте Deckhouse Platform DevFeed: [От Kubernetes-платформы к управлению гибридной распределённой инфраструктурой: встречайте Deckhouse Platform]() Original publisher: [Read original article]() Author: Manassian (Флант) Published: 2026-09-17T10:04:13Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [Kubernetes](), [on-prem](), [AI Platform](), [cloud-infrastructure](), [control-plane](), [GPU](), [PostgreSQL](), [clickhouse](), [airflow]() Tags: [airflow](), [clickhouse](), [control-plane](), [deckhouse](), [devops](), [gpu](), [kubernetes](), [on-prem](), [platform](), [postgresql](), [tag-82a17eb6b53d](), [tag-8b566f363766](), [tag-d57ff84cbcb7](), [tag-f7895e49ab8b]() ### AI overview The article announces Deckhouse Platform, which combines containerization, virtualization, and centralized cluster management. It describes ready-made infrastructure solutions for Kubernetes, virtual machines, combined workloads, AI workloads, data services, and private cloud deployments across cloud, on-premises, and edge environments. ### Source excerpt Мы объединили возможности контейнеризации, виртуализации и централизованного управления парком кластеров в один продукт -- Deckhouse Platform. Теперь контейнерами, виртуальными машинами, ИИ-нагрузками и сервисами данных можно управлять из одной точки, независимо от того, где они работают: в облаке, on-prem или на edge. В платформе уже есть готовые решения под типовые сценарии использования инфраструктуры, а под нестандартные можно собрать свою конфигурацию. Читать далее ## Kubernetes Multi-Cluster Project Karmada Reaches CNCF Graduation DevFeed: [Kubernetes Multi-Cluster Project Karmada Reaches CNCF Graduation]() Original publisher: [Read original article]() Author: Claudio Masolo Published: 2026-09-17T10:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Kubernetes](), [Orchestration](), [Cloud](), [Computing]() Tags: [ai-architecture](), [cloud](), [cluster](), [clusters](), [cncf](), [devops](), [karmada-kubernetes-cncf](), [kubernetes](), [multi-cloud](), [news](), [orchestration](), [project](), [release]() ### AI overview The CNCF announced that Karmada, a multi-cluster and multi-cloud Kubernetes orchestration project, graduated to its highest maturity tier. The announcement coincided with Karmada v1.19, which improves multi-component scheduling for AI training jobs and makes priority-based scheduling available by default in Beta. ### Source excerpt The Cloud Native Computing Foundation (CNCF) announced on September 2026 that Karmada, a multi-cluster and multi-cloud Kubernetes orchestration project, has graduated. This multi-cluster and multi-cloud Kubernetes orchestration project reached CNCF's highest maturity tier. By Claudio Masolo ## Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator DevFeed: [Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator]() Original publisher: [Read original article]() Author: Anil Joshi Published: 2026-09-17T06:43:32Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [Replication](), [export](), [Percona Server for MySQL](), [configuration](), [Server](), [Kubernetes](), [Database]() Tags: [cloud](), [configuration](), [database-trends](), [featured](), [innodb-clusterset](), [insight-for-dbas](), [kubernetes](), [kubernetes-operators](), [mysql](), [mysql-group-replication](), [mysql-high-availability](), [mysql-replication](), [open-source](), [operator](), [percona-kubernetes-operators](), [percona-operator-for-mysql](), [percona-server-for-mysql](), [percona-software](), [replication](), [uncategorized](), [yaml]() ### AI overview This tutorial explains how to configure cross-site replication between two Percona Operator for MySQL clusters to create a ClusterSet environment for disaster recovery and switchover between data-center and disaster-recovery members. It covers deploying the clusters, retrieving endpoints and cluster names, transferring credentials, and initializing the DR cluster. ### Source excerpt A while ago, we discussed the cross-site replication feature of the Percona PXC operator. Recently, a similar cross-site replication feature was introduced in the Percona (PS MySQL) operator v1.2.0, a topology based on Group Replication/InnoDB Cluster. In this blog post, we will explore how to add a DR Cluster to an existing DC Cluster to ... Continued The post Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator appeared first on Percona. ## Kubernetes Architecture: Control Plane, Scheduler, and Kubelet DevFeed: [Kubernetes Architecture: Control Plane, Scheduler, and Kubelet]() Original publisher: [Read original article]() Author: Nimesha Jinarajadasa Published: 2026-09-17T06:25:02Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [Kubernetes](), [control-plane](), [api server](), [Containers](), [etcd](), [kubectl]() Tags: [api](), [api-server](), [containers](), [control-plane](), [controllers](), [etcd](), [kubectl](), [kubernetes](), [kubernetes-architecture](), [kubernetes-networking](), [node](), [scheduler]() ### AI overview A beginner-friendly tutorial explaining how Kubernetes maintains the desired state of containerized applications. It covers the control plane, API server, etcd, controllers, scheduler, and kubelet. ### Source excerpt Learn how Kubernetes works, from the control plane and scheduler to kubelet, pods, and Services, with simple answers to interview questions. ## Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions DevFeed: [Kubernetes v1.37: Hardening Container Storage with Bind Mount Options and EmptyDir Permissions]() Original publisher: [Read original article]() Author: Nispriha Jagan; Neeraj Krishna Gopalakrishna Published: 2026-09-16T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [mount](), [Filesystems](), [chmod](), [Unix]() Tags: [chmod](), [container](), [containers](), [filesystem](), [hardening](), [kubernetes](), [linux](), [mount](), [permissions](), [storage](), [volume](), [volumes]() ### AI overview Kubernetes v1.37 adds bind mount options and emptyDir permission modes to strengthen storage security. The article explains how noexec, nosuid, nodev, Unix permissions, and the sticky bit can help enforce security policies on writable volumes. ### Source excerpt Kubernetes v1.37 brings important storage security features: emptyDir permission modes and bind mount options. They help application programmers and security professionals implement rigorous security policies, for example, prohibiting deletion of files across containers or execution of arbitrary binaries from writable volumes, directly in Kubernetes without any complicated circumvention. Linux storage and permission fundamentals Before diving into the new Kubernetes features, let us briefly review the low-level Linux security mechanisms that make them possible. Bind mount flags When Linux mounts or remounts a directory, Virtual File System (VFS) flags control what actions are permitted on that filesystem: noexec: Do not permit direct execution of any binaries on the mounted filesystem. nosuid: Do not allow set-user-identifier or set-group-identifier bits to take effect. nodev: Do not interpret character or block special devices on the file system. Directory permissions and the sticky bit Standard Unix permissions regulate access across three scopes: Owner, Group, and Others (e.g., 0755 or 0777). Beyond standard read, write, and execute bits, Linux supports the sticky bit (as in mode 01777). When applied to a directory, the sticky bit ensures that a file inside that directory can only be deleted or renamed by the file's owner or root. This is essential for shared writable directories like /tmp. Motivation for the improvements Why does Kubernetes need bind mount options and emptyDir permissions? The primary goal of these features is to increase the security of Kubernetes workloads by allowing security-related bind mount options on volume mounts. By default, volumes are bind-mounted into containers by the container runtime and kubelet without noexec, nosuid, or nodev flags. This default can undermine security. For example, with noexec missing, a compromised process can use any writable volume (emptyDir, PersistentVolume, etc.) to download, chmod +x, and execute arbitra ## Publishing a Kubernetes SIG's Images to registry.k8s.io DevFeed: [Publishing a Kubernetes SIG's Images to registry.k8s.io]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2026-09-16T18:00:00Z Content type: tutorial Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [container images](), [GitHub Actions](), [CI/CD](), [Google Cloud Platform (GCP)]() Tags: [ci-cd](), [container-image](), [container-image-registry](), [container-images](), [documentation](), [github-actions](), [google-cloud](), [guide](), [kubernetes]() ### AI overview A guide to publishing official Kubernetes SIG container images through registry.k8s.io. It explains why GHCR is unsuitable for public distribution and describes the ordered workflow involving Prow, Google Cloud Build, staging registries, and image promotion. ### Source excerpt If you're publishing container images for a Kubernetes SIG project, you might expect the same publishing workflow used by other container registries to work. That was my assumption too. My workflow successfully published the images, but they weren't publicly available. Instead, official Kubernetes project images are distributed through registry.k8s.io , the Kubernetes project's official container image registry. No single step was hard, but the steps were spread across multiple repositories and had to happen in a particular order, something I mostly learned by tripping over them. This post is the guide I wish I had at the start. It walks through that workflow end to end using Cluster Inventory API from SIG Multicluster as an example. The same process applies to eligible Kubernetes subprojects that publish official container images. My first attempt: GHCR I first tried a common GitHub release pattern: using GitHub Actions to publish images to ghcr.io on a tag push (cluster-inventory-api#40 ). The workflow succeeded, but Kubernetes GitHub organizations keep GHCR packages private, so GHCR cannot be used for public distribution. As described in the registry.k8s.io documentation , official images take a different route: Prow (the Kubernetes project's CI/CD system) picks up a tag push and runs Google Cloud Build on Kubernetes-owned infrastructure to push the image to a staging registry, and the image promoter then copies it to registry.k8s.io. The first-time setup, step by step Besides the image-owning repository, this touches three infrastructure repositories: kubernetes/k8s.io , kubernetes/test-infra , and kubernetes/org . The pieces depend on each other like this: Before you start: decide your project details Before setting up the publishing workflow, decide a few project-specific details. These values will be reused throughout the setup when creating the staging registry, configuring image builds, and setting up image promotion: , which determines the staging ## Microsoft Open-Sources TauGrid to Simplify AI Workload Management on Kubernetes DevFeed: [Microsoft Open-Sources TauGrid to Simplify AI Workload Management on Kubernetes]() Original publisher: [Read original article]() Author: Sergio De Simone Published: 2026-09-16T18:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Artificial Intelligence](), [Kubernetes](), [GPU](), [kueue](), [Go]() Tags: [agents](), [ai](), [artificial-intelligence](), [azure](), [development](), [devops](), [gpu](), [kubernetes](), [kueue](), [microsoft](), [microsoft-taugrid-open-source](), [news](), [open-source](), [orchestration]() ### AI overview Microsoft has open-sourced TauGrid, a cloud-native platform for managing, scheduling, and monitoring AI workloads on GPU-enabled Kubernetes clusters. It combines workload submission, Kueue-based queuing, KubeRay orchestration, GPU-node monitoring, and observability, while planned capabilities remain on its roadmap. ### Source excerpt Microsoft has open-sourced TauGrid, a cloud-native platform designed to manage, schedule, and monitor AI workloads on GPU-enabled Kubernetes clusters. By Sergio De Simone ## Constraining AI agents with Red Hat AI: Containment, identity, and governance DevFeed: [Constraining AI agents with Red Hat AI: Containment, identity, and governance]() Original publisher: [Read original article]() Author: Grace Ableidinger Published: 2026-09-16T13:01:59Z Content type: tutorial Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [Artificial Intelligence](), [Security](), [Zero Trust](), [Containers](), [Kubernetes](), [Architecture & Design]() Tags: [ai](), [ai-agents](), [containers](), [deployment](), [kubernetes](), [prompt-injection](), [security](), [trust]() ### AI overview This tutorial explains how to secure AI agents running on Red Hat OpenShift using containment, verifiable identity, and governance. It covers namespace isolation, quotas, sandboxing, workload identity, and admission control, with OpenClaw used in the demo. ### Source excerpt When an agent process runs on your laptop, it typically inherits anything your user has access to. Often this includes the full network stack, the file system, and the credentials sitting in memory. When integrating with GitHub, Slack, or a cloud provider, you could be one faulty permission or well-crafted prompt injection away from a security incident. The post Constraining AI agents with Red Hat AI: Containment, identity, and governance appeared first on Red Hat Developer. ## Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend DevFeed: [Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend]() Original publisher: [Read original article]() Author: Gabriele Bartolini (EnterpriseDB) and CNCF Ambassador, Rob Kenefeck (ControlPlane) Published: 2026-09-16T11:30:00Z Content type: tutorial Language: en Sources: [Cloud Native Computing Foundation]() Topics: [CloudNativePG](), [Kubernetes](), [PostgreSQL](), [Open Source](), [vendor lock-in]() Tags: [blog](), [cloudnativepg](), [docker](), [hashicorp-vault](), [helm](), [infrastructure](), [kubernetes](), [linux-foundation](), [open-source](), [postgresql](), [secrets](), [vendor-lock-in]() ### AI overview A tutorial describes deploying OpenBao on Kubernetes with a three-instance CloudNativePG PostgreSQL cluster as its storage backend. It explains certificate-based authentication and a local Kind-based test environment. ### Source excerpt Managing infrastructure secrets on Kubernetes needs a backend that is self-healing and free of vendor lock-in, and that is exactly what OpenBao (the Linux Foundation's open-source fork of HashiCorp Vault) and CloudNativePG give you: an entirely... ## Lyft Moves Streaming Fleet to Apache Flink Kubernetes Operator DevFeed: [Lyft Moves Streaming Fleet to Apache Flink Kubernetes Operator]() Original publisher: [Read original article]() Author: Mark Silvester Published: 2026-09-16T11:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [flink](), [apache-flink](), [Kubernetes](), [autoscaling](), [Deployment](), [legacy](), [Testing]() Tags: [apache-flink](), [architecture-design](), [autoscaling](), [deployment](), [development](), [devops](), [flink](), [kubernetes](), [kubernetes-operator](), [legacy](), [lyft-flink-k8s-operator](), [news](), [testing](), [upgrade]() ### AI overview Lyft moved hundreds of production Apache Flink jobs from its in-house Kubernetes operator to the Apache Flink Kubernetes Operator. The change enabled last-state upgrades, in-place autoscaling, and resource autotuning, while Lyft adapted legacy deployment specifications through its deploy API and contributed a fix for a configuration-renaming bug. ### Source excerpt Lyft has moved hundreds of production Flink jobs from a 2020 in-house Kubernetes operator to the Apache Flink Kubernetes Operator, unlocking last-state upgrades, in-place autoscaling and resource autotuning across the fleet. By Mark Silvester ## The Original Serverless Architecture is Still Here DevFeed: [The Original Serverless Architecture is Still Here]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-05-31T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [serverless architecture](), [Kubernetes](), [Orchestration](), [Docker](), [Cloud](), [Firebase](), [DynamoDB]() Tags: [amazon](), [cloud](), [containers](), [docker](), [dynamodb](), [engineering](), [firebase](), [infrastructure](), [kubernetes](), [news](), [orchestration](), [serverless](), [serverless-architecture]() ### AI overview This commentary compares Kubernetes-based architectures with serverless approaches. It explains that Kubernetes offers flexibility through containers, Helm, ingress controllers, monitoring tools, and service meshes, but requires substantial configuration and maintenance. Serverless platforms such as Firebase and Amazon Lambda abstract away server infrastructure so developers can focus on applications and stateless functions. ### Source excerpt By Kevin Dangoor This month, my colleague Dave Rosile and I went to GlueCon 2018 in sunny Denver, ... Read more ## Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases DevFeed: [Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases]() Original publisher: [Read original article]() Author: Sucahyo Ardy Prasetiyo Published: 2026-09-16T08:57:10Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [GitOps](), [Kubernetes](), [Terraform](), [argo-cd](), [ClusterControl](), [Databases](), [opentofu]() Tags: [argo-cd](), [clustercontrol](), [databases](), [gitops](), [hybrid-operations](), [infrastructure](), [kubernetes](), [opentofu](), [sovereign-dbaas](), [terraform]() ### AI overview This article describes a layered GitOps approach for Kubernetes database platforms: manage infrastructure with Terraform or OpenTofu, manage Kubernetes deployments with Argo CD, and standardize operations for operator-managed databases with ClusterControl. It explains how declarative configuration and drift reconciliation differ between Terraform and Argo CD, and compares infrastructure automation options including Atlantis and Flux tf-controller. ### Source excerpt Most platform teams already use GitOps for their Kubernetes apps. The config lives in Git, Argo CD applies it, and deployments are predictable. But look one layer down and things get messy. Infrastructure setup is often still done by hand, running Terraform locally or through scattered scripts. Database operations, especially for databases running through Kubernetes [...] The post Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases appeared first on Severalnines. ## Kubernetes attributes processor reaches v1.0.0 milestone DevFeed: [Kubernetes attributes processor reaches v1.0.0 milestone]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-09-16T04:59:27Z Content type: release Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [telemetry](), [releases](), [Kubernetes](), [Go Language]() Tags: [api](), [go](), [kubernetes](), [opentelemetry](), [releases](), [stable](), [telemetry]() ### AI overview The Kubernetes attributes processor has reached version 1.0.0 and fulfills OpenTelemetry's stability criteria for testing, benchmarking, documentation, and telemetry. The release also supports redistribution as a Go library or in binaries without API breakage. ### Source excerpt The Kubernetes attributes processor, which enriches your telemetry with Kubernetes metadata, has officially moved to v1.0.0! You can try it out on your custom distro, and it is also available as part of the latest opentelemetry-collector-contrib and opentelemetry-collector-k8s distro releases. Being v1.0.0 means the component is now verified to fulfill the 'stable' stability criteria including requirements around testing, benchmarking, documentation and telemetry stability. It also ensures you can redistribute it as a Go library or as part of your binaries without API breakage. ## Kubernetes Cost Management Tools: The Best Options 2026 DevFeed: [Kubernetes Cost Management Tools: The Best Options 2026]() Original publisher: [Read original article]() Author: Kelsey Rosen Published: 2026-09-16T00:00:00Z Content type: comparison Language: en Sources: [Harness Blog]() Topics: [Kubernetes](), [finops](), [Monitoring](), [Cloud]() Tags: [2026](), [cloud](), [compare](), [finops](), [kubernetes](), [monitoring]() ### AI overview A comparison of Kubernetes cost management tools for 2026, including Kubecost, OpenCost, and CloudZero. It explains how these tools allocate shared cloud node costs across namespaces, workloads, and pods, while accounting for idle and unallocated capacity and supporting optimization actions. ### Source excerpt Compare the best Kubernetes cost management tools for 2026, from Kubecost and OpenCost to CloudZero, on allocation depth, scale, and pricing model. | Blog ## Automate Docker Registry Creation with Harness and Terraform DevFeed: [Automate Docker Registry Creation with Harness and Terraform]() Original publisher: [Read original article]() Author: Shibam Dhar Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [docker registry](), [Kubernetes](), [Provisioning](), [Terraform](), [Infrastructure as code](), [CI/CD](), [Dockerfile]() Tags: [ci-cd](), [container-image](), [deployment](), [docker-registry](), [infrastructure-as-code](), [kubernetes](), [registry](), [terraform]() ### AI overview A tutorial shows how to use Harness Pipelines and the Harness Terraform Provider to provision a uniquely named Docker Registry, build and push a container image, and deploy it to Kubernetes. It covers Terraform execution in a CI step, passing output variables between stages, and rolling updates with automatic rollback. ### Source excerpt Provision a fresh Docker Registry with Terraform, build your container image into it, and deploy to Kubernetes in one | Blog ## Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta DevFeed: [Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta]() Original publisher: [Read original article]() Author: Kevin Torres Martinez Published: 2026-09-15T18:30:00Z Content type: release Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [cpu](), [Hardware](), [Latency](), [API](), [gRPC](), [Monitoring]() Tags: [api](), [cpu](), [hardware](), [kubernetes](), [latency](), [monitoring](), [numa](), [release](), [v1]() ### AI overview Kubernetes v1.37 graduates Pod-Level Resource Managers to Beta, disabled by default. The feature lets Kubelet resource managers use pod-level declarations for hardware placement, enabling NUMA-aligned exclusive resources for primary containers while placing sidecars in a shared pod-isolated pool. The release also adds pod-level reporting to the PodResources gRPC API. ### Source excerpt With the release of Kubernetes v1.37, the Pod-Level Resource Managers feature has graduated to Beta status (disabled by default)! First introduced as an Alpha feature in Kubernetes v1.36, this enhancement builds on Pod-Level Resources by equipping Kubelet's Topology Manager, CPU Manager, and Memory Manager to use Pod-level resource declarations (.spec.resources) directly when making hardware placement decisions. Bringing pod-level resources to node managers Before this feature, obtaining exclusive NUMA-aligned CPU cores or memory for latency-critical applications forced cluster operators into an all-or-nothing choice: assign integer resource requests to every container in the Pod, or forfeit exclusive NUMA alignment entirely. For modern workloads running lightweight sidecars (such as logging agents or telemetry exporters), allocating dedicated physical cores to auxiliary containers was wasteful. Pod-Level Resource Managers solves this challenge by enabling hybrid allocation models. The Kubelet can reserve exclusive NUMA-aligned resources for primary application containers while placing non-Guaranteed sidecars into a pod-isolated shared pool. This ensures primary workloads get unthrottled, NUMA-local performance while sidecars benefit from running in a pod-isolated shared pool, enjoying local NUMA alignment and protection from external node interference without consuming dedicated physical cores. What's new in Beta Graduating to Beta brings key operational and API enhancements: Graduation to Beta: Controlled by the PodLevelResourceManagers feature gate, available to opt in (disabled by default) in Kubernetes v1.37. PodResources API Reporting: The v1 PodResources gRPC service (PodResourcesLister) introduces top-level cpu_ids and memory fields on PodResources responses. Monitoring tools and device plugins can query pod-level exclusive assignments directly without double-counting container allocations. Getting started and providing feedback For a deep dive into the tech ## What I learned organizing KCD Lima 2026 DevFeed: [What I learned organizing KCD Lima 2026]() Original publisher: [Read original article]() Author: Ronald Requena | CNCF Ambassador Published: 2026-09-15T16:24:05Z Content type: opinion Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Kubernetes](), [data]() Tags: [2026](), [blog](), [community](), [event](), [kubernetes](), [report](), [survey]() ### AI overview Ronald Requena reflects on organizing the third Kubernetes Community Days Lima, held on July 18, 2026. He describes the event's growth, operational challenges, program, sponsorship, and attendee feedback, including 2,244 registrations, more than 900 attendees, 54 sessions, and a 4.7 out of 5 satisfaction rating. ### Source excerpt On July 18, 2026, we held the third edition of Kubernetes Community Days Lima at UTEC in Barranco. By now, we have already sent the Transparency Report to the CNCF, thanked our sponsors, and processed the... ## Scaling Federated Learning Across Docker, Kubernetes, and Slurm with NVIDIA FLARE DevFeed: [Scaling Federated Learning Across Docker, Kubernetes, and Slurm with NVIDIA FLARE]() Original publisher: [Read original article]() Author: Elizabeth Goodman Published: 2026-09-15T15:00:00Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Federated Learning](), [Docker](), [Kubernetes](), [Nvidia](), [Server](), [dataset](), [Deployment]() Tags: [architecture](), [compute](), [configuration](), [container](), [data-analytics-processing](), [data-science](), [dataset](), [deployment](), [docker](), [docker-container](), [federated-learning](), [gpu](), [job](), [kubernetes](), [nvidia](), [nvidia-flare](), [server]() ### AI overview This article explains how NVIDIA FLARE scales federated learning across sites with different infrastructure, including Docker, Kubernetes, and Slurm. Its two-layer architecture separates persistent federation services from on-demand job execution, while allowing each site to retain local control over compute, data, secrets, and scheduling. ### Source excerpt Federated learning (FL) projects often begin with a straightforward setup: one server, a few clients, and one dataset at each site. As those projects grow, the... ## Kubernetes 1.36 restores a lost guarantee for database backups DevFeed: [Kubernetes 1.36 restores a lost guarantee for database backups]() Original publisher: [Read original article]() Author: Shubham Pampattiwar Published: 2026-09-15T13:00:00Z Content type: news Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack](), [The New Stack]() Topics: [Kubernetes](), [PostgreSQL](), [Databases]() Tags: [backups](), [cncf](), [consistency](), [database](), [databases](), [kubernetes](), [post-contributed](), [postgresql](), [snapshots](), [sponsor-cncf](), [sponsored-post-contributed](), [stateful](), [storage]() ### AI overview The article explains how Kubernetes 1.36 restores coordinated snapshots for applications whose state spans multiple volumes, addressing inconsistent database backups caused by taking individual PersistentVolumeClaim snapshots at different times. ### Source excerpt It's 2 a.m., and you're restoring a PostgreSQL cluster from last night's backup. Its data directory lives on one PersistentVolumeClaim The post Kubernetes 1.36 restores a lost guarantee for database backups appeared first on The New Stack. ## Who am I ? DevFeed: [Who am I ?]() Original publisher: [Read original article]() Author: brice.dutheil@gmail.com (Brice Dutheil) Published: 2026-09-15T04:32:32.192351Z Content type: article Language: fr Sources: [The Coffee Workshop]() Topics: [Java](), [Kubernetes](), [Open Source](), [backends]() Tags: [java](), [jvm](), [kubernetes](), [open-source]() ### AI overview The author describes himself as primarily a Java and JVM developer, with experience using Kubernetes and contributing to open-source projects. He previously worked on Mockito, has spent ten years working on backends across various sectors, and currently works for BlaBlaCar. ### Source excerpt English 🇬🇧/🇺🇸 I'm mostly a Java / JVM guy. Now I'm also a Kubernetes user in surface, so I now a few system tricks. [Next page]()