# Resources Published articles for Resources. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Quiz: Python Debugging With Pdb DevFeed: [Quiz: Python Debugging With Pdb]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-12T12:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [Python](), [debugging](), [debug]() Tags: [bugs](), [course](), [debugger](), [debugging](), [how-to](), [learn](), [python](), [resources](), [tool](), [tutorial]() ### AI overview An interactive 10-question quiz that tests practical knowledge of Python's built-in pdb debugger, including inspecting variables, stepping through code, using conditional breakpoints, watching expressions, and interpreting stack traces. ### Source excerpt Practice using pdb, Python's built-in debugger. Check variables, step through code, set conditional breakpoints, and read a stack trace. ## The Python print() Function: Go Beyond the Basics DevFeed: [The Python print() Function: Go Beyond the Basics]() Original publisher: [Read original article]() Author: Real Python Published: 2026-08-25T14:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [Python](), [coding](), [Terminal](), [User Interfaces]() Tags: [coding](), [course](), [deep-dive](), [learning](), [python](), [q-a](), [resources](), [tutorial](), [video]() ### AI overview A course on Python's print() function that covers lesser-known features, common mistakes, newlines, character encodings, buffering, file output, unit-test mocking, and terminal user interfaces. ### Source excerpt Learn about Python's print() function, discover its lesser-known features, avoid common mistakes, and know when to use a better alternative. ## AWS Weekly Roundup: Student Rewards on AWS Builder Center, Local Zone in Las Vegas, and more (August 24, 2026) DevFeed: [AWS Weekly Roundup: Student Rewards on AWS Builder Center, Local Zone in Las Vegas, and more (August 24, 2026)]() Original publisher: [Read original article]() Author: Esra Kayabali Published: 2026-08-24T16:20:15Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [AWS Local Zones](), [Amazon EC2](), [Availability](), [Cloud](), [Amazon Elastic Container Service](), [Amazon Elastic Kubernetes Service]() Tags: [2026](), [amazon](), [amazon-bedrock](), [amazon-ec2](), [amazon-eks](), [amazon-workspaces](), [announcements](), [availability](), [aws](), [aws-cloudshell](), [aws-glue](), [aws-local-zones](), [cloud](), [education](), [launch](), [news](), [resources](), [week-in-review]() ### AI overview This AWS Weekly Roundup highlights Student Rewards on AWS Builder Center, which gives verified higher-education students access to premium AWS Skill Builder resources and awards AWS Credits and a certification exam voucher for earning badges. It also covers a new AWS Local Zone in Las Vegas, an additional Availability Zone in the Europe (London) Region, and batch instance termination support for Amazon EC2 Auto Scaling. The supplied article text ends mid-sentence, so the summary covers only the available content. ### Source excerpt During my time at AWS, I have always looked for opportunities to work with students. I have delivered over 50 talks at universities across the region, and watching the potential in the room is always a strong motivator. It reminds me of why I do this work, and that the students I meet today may [...] ## Securing the Infrastructure of Intelligence DevFeed: [Securing the Infrastructure of Intelligence]() Original publisher: [Read original article]() Author: 黄仁勋 Published: 2026-08-17T12:34:51Z Content type: article Language: en Sources: [NVIDIA Blog]() Topics: [Artificial Intelligence](), [cloud-infrastructure](), [Nvidia](), [OpenAI](), [Inference](), [model-deployment](), [Cloud]() Tags: [ai](), [ai-factory](), [ai-infrastructure](), [cloud](), [compute](), [corporate](), [frontier-ai](), [inference](), [infrastructure](), [model](), [nvidia](), [openai](), [platform](), [products](), [resource](), [resources](), [revenue](), [scale](), [supply-chain](), [systems]() ### AI overview NVIDIA describes a partnership with SB Energy to secure land, power and services capacity for an AI factory at the PORTS-Pike Technology Campus in Ohio, where OpenAI will be the tenant. OpenAI is expected to build and operate the facility using NVIDIA's DSX AI factory platform, with an initial capacity of 4.25 gigawatts. ### Source excerpt AI factories are the defining infrastructure of the AI era -- where compute transforms energy and data into intelligence that powers every business, industry and country. In the AI economy, compute is revenue. AI factories require a full stack of critical resources: advanced chips, packaging, memory and networking -- as well as land, power and [...] ## Working with the American Psychological Association on youth mental health and AI DevFeed: [Working with the American Psychological Association on youth mental health and AI]() Original publisher: [Read original article]() Published: 2026-08-06T06:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [Responsibility & Safety](), [responsible-ai](), [AI Development]() Tags: [ai](), [company](), [health](), [mental-health](), [openai](), [policy](), [resources](), [responsible-ai]() ### AI overview OpenAI is working with the American Psychological Association to apply psychological science to responsible AI development and use among young people. The collaboration aims to produce evidence-based guidance, family resources, and safeguards focused on youth well-being. ### Source excerpt OpenAI and the American Psychological Association advance evidence-based guidance, resources, and safeguards for responsible AI use and youth mental health. ## Python 3.14.7 and 3.13.15 are now available! DevFeed: [Python 3.14.7 and 3.13.15 are now available!]() Original publisher: [Read original article]() Author: Thomas Wouters Published: 2026-08-05T00:00:00Z Content type: release Language: en Sources: [Python Insider]() Topics: [Python 3.13](), [Python 3.14](), [releases](), [bug](), [Python]() Tags: [bug](), [community](), [contributors](), [documentation](), [github](), [python-3-13](), [python-3-14](), [releases](), [resources](), [storage](), [ubuntu](), [windows]() ### AI overview Python 3.14.7 and Python 3.13.15 are maintenance releases containing bug fixes, build improvements, and documentation changes. ### Source excerpt A pair of bug fix releases await your upgrade. ## Using Pulumi With an Internal Developer Portal | Port DevFeed: [Using Pulumi With an Internal Developer Portal | Port]() Original publisher: [Read original article]() Author: Mor Paz Published: 2026-07-30T10:17:19Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Infrastructure as code](), [Provisioning](), [GitOps](), [DevOps](), [Architecture & Design]() Tags: [building](), [catalog](), [developer](), [developer-portal](), [developers](), [devops](), [how-to](), [iac](), [infrastructure](), [infrastructure-as-code](), [internal-developer-portal](), [learn](), [platform](), [provisioning](), [resources](), [software](), [software-catalog]() ### AI overview This tutorial explains how internal developer portals can make infrastructure as code easier and safer for developers. It describes using a software catalog and reusable self-service actions to abstract IaC details and provision developer environments, with Pulumi and Port as the example. ### Source excerpt Internal developer portals can close the IaC and developer loop. Let's look at a live example of how to use Pulumi and internal developer portals. ## Using an Internal Developer Portal For Superior FinOps Visibility DevFeed: [Using an Internal Developer Portal For Superior FinOps Visibility]() Original publisher: [Read original article]() Author: Aidan O'Connor Published: 2026-07-22T12:04:29Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [finops](), [internal developer portal](), [Cloud](), [Developer experience](), [Optimization](), [data]() Tags: [cloud](), [developer-experience](), [developer-portal](), [finops](), [internal-developer-portal](), [optimization](), [platform](), [resource](), [resources](), [tools]() ### AI overview The article explains how an internal developer portal can improve FinOps visibility by combining cloud cost data with development context. It describes how this helps developers, technical leaders, engineering managers, and FinOps teams understand resource ownership, service costs, budgeting, and optimization opportunities. ### Source excerpt Port transforms FinOps by integrating and contextualizing data from multiple sources to optimize cloud costs efficiently. ## Introducing the ChatGPT for small business program DevFeed: [Introducing the ChatGPT for small business program]() Original publisher: [Read original article]() Published: 2026-07-21T17:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [Artificial Intelligence](), [OpenAI](), [OpenAI Academy](), [Prompt Engineering](), [Shopify](), [Slack]() Tags: [accounting](), [agents](), [ai](), [ai-adoption](), [business](), [chatgpt](), [content](), [customer-stories](), [ecommerce](), [events](), [guides](), [openai](), [openai-academy](), [partner](), [partners](), [product](), [resources](), [shopify](), [skills](), [small-business](), [work]() ### AI overview OpenAI launches the ChatGPT for small businesses program, offering training, AI academies, practical guides, workflows, and partner resources to help small businesses become more productive and scale. ### Source excerpt OpenAI launches the ChatGPT for Small Businesses program, helping entrepreneurs build AI skills, automate work, and grow with ChatGPT Work. ## Kubernetes Dashboard to Headlamp: A Step-by-Step Guide DevFeed: [Kubernetes Dashboard to Headlamp: A Step-by-Step Guide]() Original publisher: [Read original article]() Author: Vincent T Published: 2026-07-13T18:00:00Z Content type: tutorial Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [dashboards](), [migration](), [Web app](), [client](), [API](), [YAML](), [Authorization]() Tags: [api](), [app](), [debug](), [dev](), [features](), [forms](), [guide](), [kubernetes](), [logs](), [migration](), [resources](), [scale](), [tokens](), [ui](), [web]() ### AI overview A step-by-step guide to moving from Kubernetes Dashboard to Headlamp. It compares their deployment models, authentication, permissions, resource-management workflows, and multi-cluster capabilities, then introduces a pre-migration checklist. ### Source excerpt 1. Before you start: know what is changing 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 and can be extended with plugins. When Headlamp runs inside a cluster, it uses a Kubernetes ServiceAccount to access the API and follow RBAC rules. Kubernetes Dashboard, in contrast, only runs in-cluster and always relies on service account tokens. Understanding these models early helps you choose the right setup and permissions. 1.1 How Kubernetes Dashboard works Dashboard is a web app that runs inside your cluster. You install it in the cluster, often with Helm. You usually run one Dashboard per cluster. You often reach it with kubectl port-forward or an ingress. You log in with a Bearer token. That token is often from a service account. It includes forms that help you create resources. It leans on tables and lists for navigation. It feels like this: a UI that lives with the cluster. 1.2 How Headlamp works Headlamp acts more like a Kubernetes client with a UI. It can run on your desktop or in a cluster. It reads your kubeconfig, like kubectl does. It can show more than one cluster in one place. It favors YAML when you create or change resources. It includes list views and a visual map. You can add features with plugins. Headlamp is a UI that follows your identity, not your cluster. 1.3 What stays the same Many workflows will feel familiar: Browse workloads and resources Filter by namespace Inspect YAML, events, and status View logs Take actions your RBAC allows 1.4 What changes A few things will feel different: Login shifts from pasted tokens to kubeconfig (and sometimes SSO). Creation shifts from forms to "apply YAML." Multi-cluster becomes normal, not a special case. The map view helps you see how resources connect. 2. Pre-migration checklist This checklist helps you avoid surprises during the switch. It makes sure Head ## Helping K-12 educators build practical AI skills DevFeed: [Helping K-12 educators build practical AI skills]() Original publisher: [Read original article]() Published: 2026-07-08T10:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI Academy](), [OpenAI]() Tags: [ai](), [education](), [global-affairs](), [learn](), [openai](), [openai-academy](), [resources](), [support](), [tools](), [workshops]() ### AI overview OpenAI Academy and the Walton Family Foundation plan to host hands-on AI Skills Jams for more than 1,600 K-12 educators across U.S. cities. The workshops will focus on practical uses of AI in teaching, planning, communication, and administrative work, with continued resources available through OpenAI Academy. ### Source excerpt OpenAI Academy and the Walton Family Foundation are bringing hands-on AI Skills Jams to help K-12 educators build practical AI skills for the classroom. ## Ceph Q2 2026 Newsletter DevFeed: [Ceph Q2 2026 Newsletter]() Original publisher: [Read original article]() Author: Anthony Middleton Published: 2026-06-25T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [ceph](), [releases]() Tags: [2026](), [blog-post](), [ceph](), [ceph-events](), [collaboration](), [communication](), [community](), [contribute](), [developers](), [documentation](), [ecosystem](), [en-article](), [en-blog-post](), [event](), [governance](), [growth](), [metrics](), [newsletter](), [operational](), [operations](), [releases](), [resources](), [support]() ### AI overview The Ceph Q2 2026 Newsletter covers governance coordination, community elections, documentation initiatives, contributor resources, regional Ceph Days events, project releases, and ways to contribute. It emphasizes collaboration among users, developers, operators, and organizations across the Ceph ecosystem. ### Source excerpt During the second quarter, the Ceph Foundation focused on strengthening collaboration across the project, expanding community programs, supporting documentation efforts, and investing in regional events. This edition highlights recent governance discussions, community elections, new contributor resources, Ceph Days events, and opportunities for community members to get involved. If you have an idea for a Ceph-related event, outreach effort, or project, we encourage you to submit a funding request and work with the Foundation to help bring it to life. In This Issue ¶ Board and CSC Alignment on Community Priorities 2026 CSC Election Recap Meet the New Ceph Technical Writer Ceph Days Continue to Grow Latest Ceph Releases Community Committees and New Ways to Contribute Board and CSC Alignment on Community Priorities ¶ The Ceph Governing Board and Community Steering Committee (CSC) met this quarter to discuss the long-term health of the project, governance, documentation, community growth, and Foundation-supported initiatives. The discussion reaffirmed the distinct roles of each organization within the Ceph ecosystem. The CSC continues to provide technical governance for the project, while the Ceph Foundation focuses on community growth, events, outreach, and funding. The Linux Foundation provides operational, legal, and financial support that enables both groups to operate effectively. A significant area of focus was improving coordination between technical priorities and Foundation-supported programs. Current documentation initiatives include improvements to the documentation backport process, development of a new OSD operations guide, clarification of package and container documentation, and the removal of outdated content. The Board and CSC also discussed the future of community events and the importance of establishing clear goals and success metrics for Foundation-funded programs. Both groups reaffirmed their commitment to supporting collaboration between users, de ## See what your database is doing right now with Connections DevFeed: [See what your database is doing right now with Connections]() Original publisher: [Read original article]() Author: Brett Warminski Published: 2026-06-15T00:00:00Z Content type: release Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [debugging](), [vitess](), [Command-line interface](), [Processes]() Tags: [cli](), [database](), [databases](), [debugging](), [incident](), [logs](), [monitor](), [process](), [product](), [resources](), [tools](), [vitess]() ### AI overview Connections is a new PlanetScale CLI feature for Postgres and Vitess databases. It provides a live, refreshable view of active sessions, highlights blocked queries and waiting states, shows blocker trees, maintains recent history, and lets developers capture the observed session data for later handoff. ### Source excerpt Connections lets you monitor and manage all active connections to Postgres and Vitess databases. See active sessions, identify locking patterns, and keep debugging even when normal application connections are exhausted. ## 5 Tips to Save Money on Laravel Cloud DevFeed: [5 Tips to Save Money on Laravel Cloud]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-06-05T15:30:22Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Cloud](), [Cache](), [Databases](), [Livewire](), [Low-Code / Internal Tools]() Tags: [app](), [apps](), [billing](), [business](), [cache](), [cloud](), [compute](), [cost](), [database](), [databases](), [developer](), [growth](), [internal-tools](), [laravel](), [operations](), [pricing](), [reduce](), [resource](), [resources](), [scale]() ### AI overview Five ways to reduce Laravel Cloud costs: enable scale to zero for Flex compute, set an organization spending limit, monitor the usage page, use managed queues, and share databases and caches across apps. ### Source excerpt Five ways to reduce your Laravel Cloud bill: enable scale to zero, set a spending cap, use the usage page, switch to managed queues, and share resources. ## Reorganized ipSpace.net Segment Routing Resources DevFeed: [Reorganized ipSpace.net Segment Routing Resources]() Original publisher: [Read original article]() Published: 2026-05-11T06:18:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Segment Routing over IPv6 (SRv6)](), [Segment Routing with MPLS Labels (SR-MPLS)](), [networking]() Tags: [ipv6](), [mpls](), [resources](), [segment-routing-over-ipv6-srv6](), [segment-routing-with-mpls-labels-sr-mpls](), [sr-mpls](), [srv6]() ### AI overview The author reorganized the Segment Routing blog category into separate resources for Segment Routing with MPLS Labels (SR-MPLS) and Segment Routing over IPv6 (SRv6), ahead of a planned series covering sample SR-MPLS workshop topologies and printouts. ### Source excerpt I created nine sample SR-MPLS topologies for the ITNOG 10 SR-MPLS workshop, and of course, we ran out of time. I plan to cover those topologies and resulting printouts in a series of blog posts; to prepare for those, I cleaned up and reorganized the Segment Routing blog category, which is now split into two: Segment Routing with MPLS Labels (SR-MPLS) Segment Routing over IPv6 (SRv6) Hope you'll find them useful! Also, if you know of other non-vendor Segment Routing resources, please leave a comment, email me, or submit a pull request. ## Kubernetes v1.36: More Drivers, New Features, and the Next Era of DRA DevFeed: [Kubernetes v1.36: More Drivers, New Features, and the Next Era of DRA]() Original publisher: [Read original article]() Author: The DRA team Published: 2026-05-07T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Hardware](), [systems](), [networking](), [Availability]() Tags: [availability](), [drivers](), [feature](), [hardware](), [infrastructure](), [kubernetes](), [release](), [resource](), [resources](), [systems](), [v1]() ### AI overview Kubernetes v1.36 advances Dynamic Resource Allocation (DRA) with feature graduations, broader driver support, and improved handling of hardware and native resources. The article covers prioritized device requests, extended resource compatibility, partitionable devices, and support for sharing specialized hardware across workloads. ### Source excerpt 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 PodGroups. Driver availability continues to expand. Beyond specialized compute accelerators, the ecosystem includes support for networking and other hardware types, reflecting a move toward a more robust, hardware-agnostic infrastructure. Whether you are managing massive fleets of GPUs, need better handling of failures, or simply looking for better ways to define resource fallback options, the upgrades to DRA in 1.36 have something for you. Let's dive into the new features and graduations! Feature graduations The community has been hard at work stabilizing core DRA concepts. In Kubernetes 1.36, several highly anticipated features have graduated to Beta and Stable. Prioritized list (stable) Hardware heterogeneity is a reality in most clusters. With the Prioritized list feature, you can confidently define fallback preferences when requesting devices. Instead of hardcoding a request for a specific device model, you can specify an ordered list of preferences (e.g., "Give me an H100, but if none are available, fall back to an A100"). The scheduler will evaluate these requests in order, drastically improving scheduling flexibility and cluster utilization. Extended resource support (beta) As DRA becomes the standard for resource allocation, bridging the gap with legacy systems is crucial. The DRA Extended resource feature allows users to request resources via traditional extended resources on a Pod. This allows for a gradual transition to DRA, meaning cluster operators can migrate clusters to DRA but let application developers adopt the ResourceClaim API on their own sche ## Kubernetes v1.36: Admission Policies That Can't Be Deleted DevFeed: [Kubernetes v1.36: Admission Policies That Can't Be Deleted]() Original publisher: [Read original article]() Author: Anish Ramasekar; Benjamin Elder Published: 2026-05-04T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [configuration](), [API](), [Authorization]() Tags: [api](), [kubernetes](), [manifest](), [operations](), [policy](), [resources](), [security](), [server]() ### AI overview Kubernetes v1.36 introduces an alpha manifest-based admission control feature. Admission webhooks and CEL-based policies can be stored as files, loaded by the API server at startup, and applied before it serves requests. The approach addresses bootstrap gaps and helps prevent privileged users from deleting critical admission configuration. ### Source excerpt 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 way to prevent a privileged user from removing them. Kubernetes v1.36 introduces an alpha feature that addresses this: manifest-based admission control. It lets you define admission webhooks and CEL-based policies as files on disk, loaded by the API server at startup, before it serves any requests. The gap we're closing Most Kubernetes policy enforcement today works through the API. You create a ValidatingAdmissionPolicy or a webhook configuration as an API object, and the admission controller picks it up. This works well in steady state, but it has some fundamental limitations. During cluster bootstrap, there's a gap between when the API server starts serving requests and when your policies are created and active. If you're restoring from a backup or recovering from an etcd failure, that gap can be significant. There's also a self-protection problem. Admission webhooks and policies can't intercept operations on their own configuration resources. Kubernetes skips invoking webhooks on types like ValidatingWebhookConfiguration to avoid circular dependencies. That means a sufficiently privileged user can delete your critical admission policies, and there's nothing in the admission chain to stop them. We - Kubernetes SIG API Machinery - wanted a way to say "these policies are always on, full stop." How it works You add a staticManifestsDir field to the AdmissionConfiguration file that you already pass to the API server via --admission-control-config-file. Point it at a directory, drop your policy YAML files in there, and the API server loads them before it start ## Kubernetes v1.36: Pod-Level Resource Managers (Alpha) DevFeed: [Kubernetes v1.36: Pod-Level Resource Managers (Alpha)]() Original publisher: [Read original article]() Author: Kevin Torres Martinez Published: 2026-05-01T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Containers](), [cpu](), [Databases](), [Latency](), [Machine learning]() Tags: [backup](), [containers](), [cpu](), [database](), [kubernetes](), [latency](), [machine-learning](), [monitoring](), [performance](), [resource](), [resources]() ### AI overview Kubernetes v1.36 introduces alpha support for pod-level resource managers. The feature extends Topology, CPU, and Memory Managers from per-container allocation to pod-level resource specifications, enabling hybrid allocation models for performance-sensitive workloads while preserving NUMA alignment. ### Source excerpt Kubernetes v1.36 introduces Pod-Level Resource Managers 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 (.spec.resources), evolving them from a strictly per-container allocation model to a pod-centric one. Why do we need pod-level resource managers? When running performance-critical workloads such as machine learning (ML) training, high-frequency trading applications, or low-latency databases, you often need exclusive, NUMA-aligned resources for your primary application containers to ensure predictable performance. However, modern Kubernetes pods rarely consist of just one container. They frequently include sidecar containers for logging, monitoring, service meshes, or data ingestion. Before this feature, this created a trade-off, to get NUMA-aligned, exclusive resources for your main application, you had to allocate exclusive, integer-based CPU resources to every container in the pod. This might be wasteful for lightweight sidecars. If you didn't do this, you forfeited the pod's Guaranteed Quality of Service (QoS) class entirely, losing the performance benefits. Introducing pod-level resource managers Enabling pod-level resources support for the resource managers (via the PodLevelResourceManagers and PodLevelResources feature gates) allows the kubelet to create hybrid resource allocation models. This brings flexibility and efficiency to high-performance workloads without sacrificing NUMA alignment. Real-world use cases Here are a few practical scenarios demonstrating how this feature can be applied, depending on the configured Topology Manager scope: 1. Tightly-coupled database (Topology manager's pod scope) Consider a latency-sensitive database pod that includes a main database container, a local metrics exporter, and a backup agent sidecar. When configured with the pod Topol ## Kubernetes v1.36: In-Place Vertical Scaling for Pod-Level Resources Graduates to Beta DevFeed: [Kubernetes v1.36: In-Place Vertical Scaling for Pod-Level Resources Graduates to Beta]() Original publisher: [Read original article]() Author: Narang Dixita Sohanlal Published: 2026-04-30T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [autoscaling](), [Containers]() Tags: [containers](), [cpu](), [feature](), [kubernetes](), [resources](), [scale](), [update](), [v1]() ### AI overview Kubernetes v1.36 promotes in-place vertical scaling for pod-level resources to beta and enables it by default. Running Pods can resize their shared aggregate resource budget, often without restarting containers. ### Source excerpt 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 In-Place Pod-Level Resources Vertical Scaling has graduated to Beta in v1.36! This feature is now enabled by default via the InPlacePodLevelResourcesVerticalScaling feature gate. It allows users to update the aggregate Pod resource budget (.spec.resources) for a running Pod, often without requiring a container restart. Why Pod-level in-place resize? The Pod-level resource model simplified management for complex Pods (such as those with sidecars) by allowing containers to share a collective pool of resources. In v1.36, you can now adjust this aggregate boundary on-the-fly. This is particularly useful for Pods where containers do not have individual limits defined. These containers automatically scale their effective boundaries to fit the newly resized Pod-level dimensions, allowing you to expand the shared pool during peak demand without manual per-container recalculations. Resource inheritance and the resizePolicy When a Pod-level resize is initiated, the Kubelet treats the change as a resize event for every container that inherits its limits from the Pod-level budget. To determine whether a restart is required, the Kubelet consults the resizePolicy defined within individual containers: Non-disruptive Updates: If a container's restartPolicy is set to NotRequired, the Kubelet attempts to update the cgroup limits dynamically via the Container Runtime Interface (CRI). Disruptive Updates: If set to RestartContainer, the container will be restarted to apply the new aggregate boundary safely. Note: Currently, resizePolicy is not supported at the Pod level. The Kubelet always defers to individual container settings to decide if an update can be applied in-place or requires a restart. Example: Scaling a shared resource pool In this scenario, a Pod is defined with a 2 CPU pod-level ## Inside Claude Code, OpenAI Codex, and HuggingFace's ML Engineer Agent : 📚 Tokenizer #26 DevFeed: [Inside Claude Code, OpenAI Codex, and HuggingFace's ML Engineer Agent : 📚 Tokenizer #26]() Original publisher: [Read original article]() Author: Sairam Sundaresan Published: 2026-04-30T13:12:59Z Content type: article Language: en Sources: [Gradient Ascent]() Topics: [Claude Code](), [Artificial Intelligence](), [codex](), [Machine learning](), [OpenAI](), [Open Source Models & Datasets](), [Library](), [data]() Tags: [agent](), [ai](), [claude-code](), [codex](), [coding](), [ml](), [multi-agent](), [newsletter](), [openai](), [resources]() ### AI overview This issue of The Tokenizer curates AI and machine-learning resources, including papers on multi-agent organization and iterative reasoning, videos about OpenAI Codex and agent complexity, a source-code walkthrough of Claude Code, tools for coding-agent context and computer control, and Hugging Face's open-source ML engineer agent. ### Source excerpt This week's most valuable AI Resources ## Anonymous credentials: an illustrated primer (Part 2) DevFeed: [Anonymous credentials: an illustrated primer (Part 2)]() Original publisher: [Read original article]() Author: Matthew Green Published: 2026-04-17T17:19:15Z Content type: tutorial Language: en Sources: [Matthew Green]() Topics: [Cryptography](), [Security, Privacy and Abuse Prevention]() Tags: [ai](), [anonymous-credentials](), [artificial-intelligence](), [attacks](), [credentials](), [cybersecurity](), [privacy](), [resources](), [security](), [state](), [technology]() ### AI overview Part two of an illustrated primer on anonymous credentials moves from the theoretical overview in part one toward practical discussion of real-world credential systems. It explains privacy-preserving authentication, credential showing without linkability, limits on credential reuse, cloning attacks, and expressive claims. ### Source excerpt This is the second in a series of posts about anonymous credentials. You can find the first part here. In the previous post, we introduced the notion of anonymous credentials as a technique that allows users to authenticate to a website without sacrificing their privacy. As a quick reminder, an anonymous credential system consists of ... Continue reading Anonymous credentials: an illustrated primer (Part 2) -> ## Healthcare DevFeed: [Healthcare]() Original publisher: [Read original article]() Published: 2026-04-10T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [ChatGPT](), [Prompt Engineering]() Tags: [ai](), [ai-tools](), [chatgpt](), [documentation](), [healthcare](), [openai-academy](), [resources]() ### AI overview This healthcare resource presents practical ways clinicians can use AI and ChatGPT for Healthcare in clinical workflows, including evidence review, guideline reconciliation, documentation, prior authorizations, and patient-information summarization. It highlights a secure, HIPAA-compliant workspace with cited answers from trusted medical sources. ### Source excerpt Explore how clinicians use ChatGPT to support diagnosis, documentation, and patient care with secure, HIPAA-compliant AI tools. ## Financial services DevFeed: [Financial services]() Original publisher: [Read original article]() Published: 2026-04-10T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [Prompt Engineering](), [Data analysis]() Tags: [ai](), [analysis](), [data](), [explore](), [financial-services](), [guides](), [openai](), [openai-academy](), [policy](), [resources](), [scale](), [search](), [tax](), [tools](), [workflows]() ### AI overview A curated collection of OpenAI resources for financial services organizations, covering AI evaluation, adoption, deployment, and scaling in regulated environments. It includes prompts and guidance for financial analysis, research, policy and tax interpretation, document analysis, data extraction, and business workflows. ### Source excerpt Explore AI resources for financial services, including prompt packs, GPTs, guides, and tools to help institutions deploy and scale AI securely. ## AI Resource Roundup: Claude Code, Codex, and Coding Agents DevFeed: [AI Resource Roundup: Claude Code, Codex, and Coding Agents]() Original publisher: [Read original article]() Author: Sairam Sundaresan Published: 2026-04-09T12:03:36Z Content type: article Language: en Sources: [Gradient Ascent]() Topics: [Claude Code](), [Artificial Intelligence](), [codex]() Tags: [ai](), [claude-code](), [codex](), [resources]() ### AI overview This newsletter edition curates AI and ML resources about production agents, coding-agent architecture, evaluation benchmarks, RAG pipelines, and model training. It highlights examples involving Claude Code and OpenAI Codex, alongside papers, videos, tools, and a Claude Code walkthrough. ### Source excerpt This week's most valuable AI resources [Next page]()