15 Jun 2026

feedHacker News

Anthropic's Safety Superpower

Comments

15 Jun 2026 10:06am GMT

feedLinuxiac

ZeroFS Turns S3 Buckets Into Linux Filesystems and Block Devices

ZeroFS Turns S3 Buckets Into Linux Filesystems and Block Devices

ZeroFS is a new open-source project that exposes S3-compatible storage over NFS, 9P, and NBD for Linux systems.

15 Jun 2026 9:48am GMT

feedHacker News

Show HN: I wrote a C++ ray tracer from scratch without AI

Comments

15 Jun 2026 9:34am GMT

What the Fuck Happened to Nerds

Comments

15 Jun 2026 8:23am GMT

feedKubernetes Blog

Spotlight on SIG Storage

In our ongoing SIG Spotlight series, we shine a light on the groups that keep the Kubernetes project moving forward. This time, we catch up with SIG Storage, the group responsible for persistent data, volume management, and the interfaces that connect Kubernetes workloads to the storage systems beneath them.

We spoke with Xing Yang, Co-Chair of SIG Storage and Software Engineer at VMware by Broadcom, about the SIG's history, the features shipping in recent Kubernetes releases, and where storage in Kubernetes is headed as AI workloads become the norm.

Introductions

Could you introduce yourself and share your role(s) within SIG Storage?

My name is Xing Yang, a software engineer at VMware by Broadcom. I'm a co-chair in SIG Storage, alongside another co-chair Saad Ali from Google. There are also two Tech Leads in SIG Storage: Michelle Au from Google and Jan Šafránek from Red Hat.

What first drew you to storage in Kubernetes, and how did you start contributing?

I have always been working in the storage domain, so SIG Storage was a natural place for me to get started when I began to learn Kubernetes. I started attending SIG Storage meetings, trying to figure out what I could do to help. This was before the first Container Storage Interface (CSI) release - lots of things were still evolving. It was a very exciting time.

What subprojects or areas do you actively maintain or review today?

I'm a maintainer in Kubernetes CSI. There are multiple CSI sidecars - such as csi-provisioner, csi-attacher, csi-resizer, and csi-snapshotter - that we need to release following every Kubernetes release. I'm also a co-chair for a Data Protection Working Group co-sponsored by SIG Storage and SIG Apps. Several features have come out of that WG aimed at filling gaps in data protection support within Kubernetes. One is Volume Group Snapshot, which provides crash-consistent group snapshots for multiple volumes used by an application. Changed Block Tracking (CBT) is another critical feature from the DP WG designed to support efficient backups.

About SIG Storage

For folks who are new: what is SIG Storage, in your own words? What problems in Kubernetes are you trying to solve?

SIG Storage is a Special Interest Group focused on how to provide storage to containers running in your Kubernetes cluster. We define standard interfaces so that a storage vendor can write a driver and have its underlying storage system consumed by containers in Kubernetes.

Why does Kubernetes need a dedicated storage SIG? What makes storage hard in a distributed system?

When Kubernetes was first introduced, it was meant for stateless workloads only. Container applications were regarded as ephemeral and therefore did not need to persist data. However, that changed drastically. Stateful workloads started running in Kubernetes, and we needed a dedicated SIG to tackle the associated storage challenges. PersistentVolumeClaims, PersistentVolumes, and StorageClasses were all introduced to provision data volumes for applications running in Kubernetes.

How did SIG Storage originally form, and how has its mission changed over time?

SIG Storage was formed to address the challenges of handling persistent data within Kubernetes. Initially, PersistentVolumes were implemented as in-tree plugins, and the SIG managed those plugins while developing core storage primitives like PersistentVolumes and PersistentVolumeClaims.

Container Storage Interface (CSI) was introduced later and played a crucial role in simplifying storage integration, enabling third-party storage providers to develop and maintain their own out-of-tree plugins without modifying Kubernetes core code.

With basic integration addressed by CSI, the SIG's mission expanded to include advanced storage features that leverage the new interface. The SIG has also expanded its scope to support object storage through the Container Object Storage Interface (COSI).

Current work and roadmap

What are the top features SIG Storage is actively working on right now?

The Data Protection WG has been working on a couple of exciting features:

Another feature worth highlighting is Container Object Storage Interface (COSI). COSI provides a standard interface for provisioning and consuming object storage buckets in Kubernetes - standardizing object storage for containerized applications much like CSI did for block and file storage. COSI is now transitioning to v1alpha2, with plans for promotion to Beta in a future release.

What recent work from SIG Storage do you consider a "win" for users?

The graduation of VolumeAttributesClass to GA in Kubernetes v1.34 is a major win for users managing stateful workloads. Previously, changing volume attributes like IOPS or throughput required out-of-band actions or disruptive operations. Now, users can dynamically tune storage properties such as IOPS or throughput directly through the Kubernetes API - scaling up for peak loads or down to optimize costs - without external processes or downtime.

VolumeAttributesClass enables dynamic modification of storage characteristics without recreating the volume. This completes the picture by allowing users to tune both capacity and other storage properties dynamically, just as they can now tune both CPU and memory for compute.

Looking ahead one or two releases, what's on the roadmap that people should watch for?

I'd like to draw attention to the Volume Health feature. This feature is designed to offer critical visibility into the operational status and integrity of persistent volumes. By enabling storage drivers and the Kubernetes control plane to report issues, it allows for proactive monitoring and identification of volume-related problems.

Currently, volume health information is reported via non-persistent events. We are actively investigating enhancements to this feature with the goal of supporting automated remediation capabilities in the future.

Are there areas where you'd really like more discussion or help from the community?

We always need help from the community to fix bugs, add tests, and help with reviews.

We'd also like to get feedback on the Alpha feature Mutable PV Affinity, which was introduced in Kubernetes v1.35. Use cases include migrating volumes from zonal to regional storage or migrating from one disk type to another.

Another topic is volume replication. It was raised at KubeCon Atlanta and has been discussed in the Data Protection WG. Community members interested in this topic are encouraged to join the DP WG meetings.

What are the biggest challenges users face today when running stateful workloads on Kubernetes?

While Kubernetes has moved stateful workloads - like databases and AI pipelines - into the mainstream, managing "state" in a system designed for ephemerality remains difficult:

Storage and AI

How do you see storage evolving in Kubernetes over the next few years, especially as AI/ML workloads grow?

I see several trends shaping storage in Kubernetes as it evolves from a container orchestrator into the "Operating System" for AI:


SIG Storage continues to tackle some of the hardest problems in Kubernetes: keeping stateful applications running reliably, making storage operations transparent and composable, and now scaling up to meet the demands of AI-era workloads. Whether you're a user managing databases in production or a developer curious about storage internals, there's a place for you in SIG Storage.

If you'd like to get involved, check out the SIG Storage community page and join the bi-weekly meetings. You can also find the SIG on Slack at #sig-storage.

15 Jun 2026 12:00am GMT

14 Jun 2026

feedLinuxiac

Linuxiac Weekly Wrap-Up: Week 24, 2026 (June 8 – 14)

Linuxiac Weekly Wrap-Up: Week 24, 2026 (June 8 – 14)

Catch up on the latest Linux news: Alpine 3.24, Linux kernel 7.1, COSMIC Desktop 1.0.16, Wine 11.11, Yserver is a new X11 server for Linux, and more.

14 Jun 2026 11:51pm GMT

DietPi 10.5 Enables KMS/DRM by Default on Raspberry Pi

DietPi 10.5 Enables KMS/DRM by Default on Raspberry Pi

DietPi 10.5 switches Raspberry Pi GUI installs to KMS/DRM by default, updates camera handling, and reworks display configuration.

14 Jun 2026 10:59pm GMT

feedOMG! Ubuntu

Linux 7.1 brings new NTFS driver, Steam Deck OLED audio fix + more

Linux 7.1 arrives with a rewritten NTFS driver, Apple Silicon battery reporting, and Steam Deck OLED audio fixes alongside massive legacy code removals.

You're reading Linux 7.1 brings new NTFS driver, Steam Deck OLED audio fix + more, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

14 Jun 2026 8:21pm GMT

12 Jun 2026

feedUbuntu blog

A decade of Ubuntu on IBM Z and IBM LinuxONE

This year we celebrate a decade of Ubuntu Server support on the s390x architecture: marking a long-standing collaboration between Canonical and IBM that began at LinuxCon 2015. The first release happened on April 21, 2016, bringing Ubuntu 16.04 LTS (Xenial Xerus) to IBM Z and IBM LinuxONE platforms. A first for Ubuntu on IBM That […]

12 Jun 2026 6:13pm GMT

11 Jun 2026

feedUbuntu blog

AI at the edge: simplifying infrastructure with Cisco and Canonical

Legacy infrastructure was not designed for the requirements of the AI era. While large-scale model training remains centralized in data centers, test-time inference is rapidly shifting to the edge to reduce latency and bandwidth consumption. This shift creates a new frontier for enterprise AI, but deploying at the edge introduces significant manual complexity, interoperability issues, […]

11 Jun 2026 7:25pm GMT

feedOMG! Ubuntu

LibreOffice gives its Ribbon-style UI a pop of colour

You'll be able to customise the look of LibreOffice's Tabbed UI in the free office suite's next major release, which his due out in August 2026. LibreOffice 26.8's Tabbed UI (also known as the Notebookbar and modelled after the Ribbon in Microsoft Office) can show a colourful background when application theming is enabled under Tools > Options > Appearance. A blue shade is used by default but you can pick or set any colour you like. In the 'Customisations' section, first selected the Writer, Calc, Impress or Data Notebookbar value, then use the dropdown to chance the colour. Click apply […]

You're reading LibreOffice gives its Ribbon-style UI a pop of colour, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

11 Jun 2026 6:48pm GMT

feedUbuntu blog

The next era of telco clouds: get open infrastructure choice with Sylva and Canonical Kubernetes

Achieving vendor neutrality in telco clouds requires an infrastructure layer that respects open standards, without wrapping them in rigid platform layers. By combining upstream alignment with up to 15 years of support longevity, Canonical's approach to Sylva is built around a requirement that matters deeply to telcos: follow upstream cloud-native innovation when developing and evolving platforms, then rely on long-term support to keep production environments stable, trusted, and operationally predictable.

11 Jun 2026 10:34am GMT

10 Jun 2026

feedOMG! Ubuntu

Microsoft brings Rust Coreutils to Windows – natively

Windows logo with a hand reaching out to grab the Coreutils logo.Microsoft has released Coreutils for Windows, allowing a stack of familiar "Linux-like" command-line utilities to run natively on Windows. The project is based on uutils, the Rust-based reimplementation of GNU coreutils that Ubuntu (mostly) has adopted in recent releases. Microsoft's package bundles uutils' coreutils and findutils as well as a GNU-compatible grep in a single binary. It offers tools like cat, cp, ls, mv and uptime. Commands that use POSIX-only features are excluded, meaning chmod, chown, kill and others aren't included. What's notable - *nix tools working their way into the Windows ecosystem is notable - is that this isn't […]

You're reading Microsoft brings Rust Coreutils to Windows - natively, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

10 Jun 2026 4:21pm GMT

09 Jun 2026

feedJavaScript Weekly

VoidZero → Cloudflare, and Angular 22 lands

#​789 - June 9, 2026

Read on the Web

JavaScript Weekly

VoidZero is Joining Cloudflare - One of the year's big moves in JS tooling, as told by Evan himself. The company he founded to build Vite, Vitest, Rolldown, Oxc, etc. is joining Cloudflare. He's candid about why (monetization is hard). Good news: all projects stay MIT-licensed, and Evan and co remain in charge.

Evan You

💰 In the Vite team's post, they reveal Cloudflare is starting a $1 million fund to support Vite ecosystem maintainers and contributors.

Come for Great PostgreSQL Talks - Virtual and Free - Attend talks about PostgreSQL-backed app development at POSETTE: An Event for Postgres 2026 (16-18 June). Join live and chat directly with PostgreSQL speakers, other developers and users. There is also swag waiting for you. Register for updates.

Microsoft | AMD sponsor

Announcing Angular v22 - Google's batteries-included framework graduates three big features to stable/production-ready: Signal Forms, Angular Aria, and asynchronous reactivity. The router also adds experimental support for the native browser Navigation API.

The Angular Team

IN BRIEF:

RELEASES:

📖 Articles and Videos

Modern Engineering Values - "I cannot believe that I used to write code by hand!" The creator of Jest and Fate says that as agents write more software, the engineering values that matter shift, with ownership, taste, and strict-but-fast feedback loops at the fore.

Christoph Nakazawa

'I Wish Deno Would Keep Doing What It Does Best' - A Deno fan argues that chasing Node.js/npm compatibility is costing the runtime its edge as a zero-config, web-standards, all-in-one-binary experience.

Hong Minhee

How Is Your App Performing in Production? - Ship a release this morning. By tonight you can know if the app got faster, slower, or worse for any specific cohort of users.

Expo sponsor

What Bun Can Tell Us About AI and Open Source - An analyst looks at Bun, whose code is increasingly AI-produced rather than human-written, as a bellwether for whether AI-authored core infrastructure is sustainable.

Stephen O'Grady (RedMonk)

📺 All 17 TanStack Projects in One App - TanStack is now a huge suite of libraries, and if anyone can pull them all into one app, Jack can! Jack Herrington

📄 Everything You Need to Know About Source Maps Neciu Dan

📄 How TypeScript Infers Type Variables Nicolas Laurent

🛠 Code & Tools

Geometric.js: A Library for Doing Geometry - Created by someone who works on graphics for the NYT, this elegant library lets you work with polygons, bounding boxes, reflection, interpolation, rotation, and the like (examples). Does one polygon intersect with another? There's a function for that.

Harry Stevens (The New York Times)

Ship Real-Time Features Without a Second Database - TimescaleDB extends Postgres for live analytics on event data. No pipeline, no extra infrastructure. $1000 credit.

Tiger Data (creators of TimescaleDB) sponsor

Micromodal.js: A Tiny Library for Accessible Modal Dialogs - No-dependency library for WAI-ARIA guideline-compliant modal dialogs. Offers extra polish versus <dialog>, with hooks, scroll-locking, in/out transitions, and click backdrop to dismiss.

Ghosh and Singh

📝 PDFSlick 4.0: View and Interact with PDFs in JS Apps - A PDF viewer for React, Solid, Svelte & vanilla JS apps that goes from simple PDF viewing up to working with multiple, large documents with annotations. Demo.

Vancho Stojkov

babel-plugin-zod-hoist: Hoist Zod Schema Definitions to the Top of the File - From the creator of Slonik comes a way to make Zod validation significantly faster.

Gajus Kuizinas

📰 Classifieds

Flaky tests slowing down dev? Meticulous gives engineers confidence to ship faster by autonomously testing every edge case of your web app.

🏢 Clerk now shows your top orgs by member count - ranked, visualized, with per-tenant detail links. Know how your B2B accounts are growing.

📄 Skip the HTML-to-PDF headaches. Foxit's DocGen API turns Word templates and JSON into clean, formatted PDFs in one API call.

Build and deploy durable AI agents in TypeScript, without managing your own infrastructure. Ship your first agent with Trigger.dev.

📢 Elsewhere in the ecosystem

  • Oxide Computer Company's Mitos ASCII Tool (above) converts images into ASCII text illustrations and animations, by way of a built-in livecoding environment (built upon the fantastic play.core).

  • 🔁 replacements.fyi, from the e18e team, is a handy way to find replacements for npm packages of your choice, whether that's a simpler package, a code snippet that does the same thing, or a native API.

  • ⚡ Add Obs.js to a page and it adds classes to <html> to customize the UX based on how much performance is available (e.g. bandwidth, CPU, latency). Harry Roberts explains further.

  • 🕹️ Raymond Camden set out to see if Chrome's built-in AI could play Zork 1, the classic text adventure game.

09 Jun 2026 12:00am GMT

02 Jun 2026

feedJavaScript Weekly

How to vet an npm package in 2026

#​788 - June 2, 2026

Read on the Web

JavaScript Weekly

Hocuspocus 4: Add Real-Time Collaboration to Any App - A plug-and-play real-time collaboration backend based on Yjs so you can quickly and safely wire up multi-user collaborative experiences into a JavaScript app. It runs on Node, Bun, Deno, or Cloudflare Workers. GitHub repo.

Tiptap

Still Writing Tests Manually? Meticulous AI Is Here - Notion, Dropbox, Wiz and LaunchDarkly now use a testing paradigm they can't work without. Built by former Palantir engineers, Meticulous automatically creates an evolving suite of E2E UI tests, delivering exhaustive coverage with no developer effort.

Meticulous sponsor

How to Evaluate an npm Package: 2026 Edition - A practical checklist for vetting packages beyond star counts, covering provenance attestation, install scripts, CI quality, and maintainer responsiveness. Learn to spot the red flags before you npm install.

Gabor Koos

IN BRIEF:

RELEASES:

📖 Articles and Videos

🤖 Using AI to Write Better Code More Slowly - A prolific JavaScript developer says LLMs aren't just for pumping out bad code quickly, they can indeed help you write higher quality code more slowly.

Nolan Lawson

TypeScript Tips Everyone Should Know - A concise set of tips for safer and cleaner code, as well as a reminder that while TypeScript can improve correctness, it doesn't guarantee good architecture or eliminate runtime bugs.

Matt Smith

Your Partition Scheme Made Sense. Then the Data Got Big - TimescaleDB extends Postgres so analytics queries stay fast at scale. No pipeline, no second database. $1000 credit.

Tiger Data (creators of TimescaleDB) sponsor

Intentionally Blocking Rendering with JavaScript - "Sometimes an inline render-blocking script is a small price to pay for avoiding aggressive layout shifts."

Jay Freestone

Why Does tsgo Use So Much Memory? - A look into the Go-powered TypeScript 7 compiler and why it can chew through gigabytes on a large project.

Zack Radisic

📄 CSS vs. JavaScript for Web Animations - Underlying performance differences and guidance on when to pick which approach. Josh W. Comeau

📄 Your Recursion is Lying to You - ES2015 specified tail call optimization, but most engines in 2026 don't support it. Gabor Koos

📄 How We Cut Build Times by Two-Thirds by Deleting Our CMS - The story of Sentry's Gatsby to Astro migration. Eli Lennox (Sentry)

📄 Creating a VS Code Agent Hook to Respond to File Changes Nicholas C. Zakas

🛠 Code & Tools

📊 Plotly 3.6: The Declarative Graphing Library - A long-standing library, also widely used in the Python and R ecosystems, that offers over 50 visualization types, from basic charts and graphs to maps, plots, and heatmaps.

Plotly, Inc.

Expo UI Is Stable. Real SwiftUI and Compose from JS - One import. SwiftUI on iOS, Jetpack Compose on Android. Plus native drop-in replacements for 7 community packages.

Expo sponsor

Component Party: A Rosetta Stone of UI Libraries - A side-by-side code snippet comparison of frameworks including React, Vue, Svelte, Angular, Ember, and more obscure options. Recent updates have extended Angular and Svelte coverage, plus added Ripple and Ember Polaris to the mix.

Mathieu Schimmerling

🎉 tsParticles 4: A Particle Engine for Web Effects - If you want a confetti cannon, fireworks, ribbons, fireflies, snow, or similar effects on your pages, this is for you. Supports all major frameworks and vanilla JS. You can see some live demos here.

Matteo Bruni

📰 Classifieds

🚀 Handsontable's 342K-line JS→TS migration is ready - best-in-class docs so you can build faster, with confidence.

⚡ Add production-ready auth to Next.js in minutes. Run clerk init, configure from the terminal, skip the dashboard: clerk.com/cli.

🤖 A fleet of coding agents that ship real PRs. SWE-AF orchestrates Claude Code, Codex & Gemini into reviewed, production-grade pull requests - not demos.

📢 Elsewhere in the ecosystem

02 Jun 2026 12:00am GMT

01 Jun 2026

feedKubernetes Blog

From Kubernetes Dashboard to Headlamp: Understanding the Transition

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.

The Kubernetes Dashboard project has now been archived. We deeply respect the work the team did and the role Dashboard played in making Kubernetes more approachable for so many users.

Headlamp builds on that foundation and carries it forward. It keeps the clarity of a visual interface while adding capabilities that match how Kubernetes is used today. This includes multi-cluster visibility, application-centric views, extensibility through plugins, and flexible deployment options that work both in-cluster and on the desktop.

This guide is meant to help you navigate that transition with confidence. Before diving into the mechanics of migration, we start with familiar ground by looking at how common Kubernetes Dashboard workflows map to Headlamp. We also cover what stays the same and what improves after the switch. The goal is not just to replace a tool, but to honor a user-centered legacy and help you land in a UI that can grow with you as your Kubernetes usage evolves.

Mapping Kubernetes Dashboard workloads to Headlamp

If you have used Kubernetes Dashboard before, many workflows in Headlamp will feel familiar. Headlamp does not introduce a new way of thinking. Instead, it builds on workloads users already know and extends them in practical ways. The focus is continuity. What worked before still works, with more room to grow.

Viewing workloads and resources

In Kubernetes Dashboard, most users started by browsing workloads like pods, deployments, services, and namespaces. Headlamp keeps this same starting point. Workloads are easy to find and inspect, and moving between namespaces and clusters is simpler. Resources are still organized in familiar ways, and navigation feels smoother, especially when you work across multiple environments.

Viewing Kubernetes workloads and resources in the Headlamp interface

Editing and interacting with resources

Like Kubernetes Dashboard, Headlamp lets you view and edit manifests directly in the UI based on your permissions. You can delete resources, scale workloads, or update configurations from the interface. All actions follow standard Kubernetes RBAC. If you could perform an action in Dashboard, you will find the same capability in Headlamp, with the same respect for access controls.

Editing and interacting with Kubernetes resources in the Headlamp user interface

Understanding relationships

Where Headlamp begins to expand the experience is in how it presents relationships between resources. In addition to list views, Headlamp offers visual ways to see how workloads, services, and configurations connect. This helps provide context without changing the underlying workloads users already rely on.

Visualizing relationships between Kubernetes workloads and services in Headlamp

At a high level, the tasks you performed in Kubernetes Dashboard are still there. Headlamp keeps familiar workflows while making it easier to scale as clusters, teams, and applications grow.

Where Headlamp goes beyond Kubernetes Dashboard

Expanding from single cluster to multi-cluster workflows

Kubernetes Dashboard was designed to work with one cluster at a time. That model worked well for simple setups, but it became limiting as teams adopted multiple environments. Headlamp expands this view by letting you work with multiple clusters from a single interface without switching tools or losing context. This makes it easier to manage development, staging, and production environments side by side.

Expanding from single cluster to multi-cluster workflows using Headlamp

For teams running Kubernetes in more than one place, this shift reduces friction. You can stay oriented and move between clusters with confidence.

From resource lists to application context with Projects

Projects give you an application-centered way to view Kubernetes. Instead of jumping between lists, you can group related workloads, services, and supporting resources in one place. This makes applications easier to understand. You can see what belongs together, track changes in context, and troubleshoot without scanning the cluster piece by piece.

Projects are built on native Kubernetes concepts. Namespaces, labels, and RBAC continue to work the same way they always have. Headlamp adds a visual layer that brings related resources together.

Projects are optional. You can still work at the individual resource level when that fits your task. When you need more context, Projects help you step back and see the bigger picture.

Application Projects view in Headlamp grouping related Kubernetes resources

Extend the Headlamp UI with plugins

Headlamp can be extended through plugins that bring common workflows directly into the UI. Instead of switching tools, you work in one place with the same context.

Adding plugins from the plugin catalog in the Headlamp interface

For example, the Flux plugin brings GitOps workflows into Headlamp. It allows teams to view application state alongside the Kubernetes resources that Flux manages, making it easier to understand how changes in Git relate to what is running in the cluster.

Viewing and managing GitOps resources in Headlamp using the Flux plugin

The AI Assistant follows a similar pattern. It adds a conversational layer to the UI that helps users understand what they are seeing, troubleshoot issues, or take action. All of this happens in the same screen where the problem appears.

Using the AI assistant in Headlamp to understand and troubleshoot Kubernetes resources

Building your own plugins

Plugins are optional and not limited to community-built extensions. Platform and project teams can also create their own plugins. This allows organizations to add custom integrations that match their specific workflows and internal tooling, while keeping the user experience consistent.

Choosing how and where Headlamp runs

Headlamp gives teams flexibility in how they use a Kubernetes UI. You can run it directly in a cluster, use it as a desktop application, or combine both approaches based on your needs.

Running Headlamp in-cluster works well for shared environments. It provides a centrally managed UI with controlled access and fits naturally into Kubernetes setups, following the same authentication and RBAC rules as other in-cluster components.

Running Headlamp as an in-cluster browser-based application

The desktop application is often a better fit for local development and onboarding. It also works well when you need to manage multiple clusters from one place. Users can connect using their existing kubeconfig without deploying anything into the cluster.

Using Headlamp as a desktop application to manage Kubernetes clusters locally

These options are not mutually exclusive. Many teams use the desktop app for day-to-day work, while relying on an in-cluster deployment for shared or production environments.

Preparing for the Migration

Before moving from Kubernetes Dashboard to Headlamp, it can be helpful to pause and take stock of how you use the Dashboard today. A little reflection up front can go a long way toward making the transition feel smooth and familiar.

Start by noting which clusters and namespaces you access and how authentication works. Headlamp relies on standard Kubernetes authentication and RBAC. In most cases, existing access models carry over without change. If users already connect using kubeconfig files or service accounts, they will be able to access the same resources in Headlamp.

It is also useful to think about the workflows that matter most to your team. Some users rely on Dashboard for quick inspection or troubleshooting, while others use it for lightweight edits or validation. Headlamp supports these same workflows and adds optional capabilities on top. Knowing what you rely on today helps the transition feel predictable and confidence building.

If you would like to explore Headlamp or try it out before migrating, you can learn more at headlamp.dev.

This blog focused on understanding the transition and what to expect. A step by step migration guide is coming soon and will walk through installation and migration in detail.

01 Jun 2026 6:00pm GMT

26 May 2026

feedKubernetes Blog

Reconciling the Past: Correcting Records for Unfixed Kubernetes CVEs

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 Kubernetes CVE Feed, we have identified some discrepancies. CVE records for a few older, unfixed issues incorrectly include a fixed version field.

The Kubernetes Security Response Committee (SRC) will correct the affected CVE records on June 1, 2026. This may result in vulnerability scanners identifying these vulnerabilities in places where they were previously not detected.

To help reduce confusion, this post provides a technical update on three vulnerabilities that were disclosed in previous years but remain unfixed: CVE-2020-8561, CVE-2020-8562, and CVE-2021-25740.

Why we are updating these records now

While these vulnerabilities have been public for several years, the recent work to generate official Open Source Vulnerabilities (OSV) files revealed that their corresponding CVE records did not accurately reflect their status. Specifically, some records suggested a fixed version existed, when in reality, these issues are architectural design trade-offs that cannot be fully remediated through code without breaking fundamental Kubernetes functionality.

Correcting these records is vital for the community for:

For completeness, we should also mention that CVE-2020-8554 is an unfixed CVE with a correct CVE record stating that it affects all versions. That record will also be updated to use a more-standardized version number format.

Technical analysis of unfixed architectural risks

The following vulnerabilities will not be fixed by the Kubernetes project. GitHub issues remain the best reference for the technical mechanics of these flaws.

CVE-2020-8561: Webhook redirect in kube-apiserver

CVE-2020-8562: Proxy bypass via DNS TOCTOU

CVE-2021-25740: Cross-namespace forwarding via Endpoints

Note:

On June 1, 2026, these CVE records will be updated to correctly reflect the fact that all versions are affected. You may see them begin to appear in vulnerability scanner results.

Required actions for administrators

The Kubernetes project recommends a secure by configuration approach to manage these persistent risks:

Vulnerability Action item Severity score (Rating) Command / configuration
CVE-2020-8561 Restrict Log Verbosity 4.1 (Medium) Ensure --v is set to < 10 and --profiling=false.
CVE-2020-8562 Enforce DNS Consistency 3.1 (Low) Deploy dnsmasq or a similar caching resolver on control plane nodes.
CVE-2021-25740 Hardened RBAC 3.1 (Low) kubectl auth reconcile to remove Endpoints write access from broad roles.

The RBAC action for CVE-2021-25740 applies when your cluster uses RBAC authorization mode, which is the default for clusters created with standard Kubernetes tooling. Administrators should independently test and validate these configurations in a non-production environment, assessing the architectural risks against their specific threat model and risk tolerance.

Conclusion: maturity through transparency

The effort to reconcile these records is a sign of a maturing security ecosystem. By moving away from the "patch-only" mindset and accurately documenting architectural debt, the Kubernetes project provides the community with the high-fidelity data needed to secure modern cloud native infrastructure.

We would like to thank the security researchers-QiQi Xu, Javier Provecho, and others-who identified these risks, and the SIG Security Tooling contributors who continue to refine our official feeds. Special shoutout to Rory McCune for sharing information around these CVEs through his blog posts.

Update 2026/06/01: Today, the Kubernetes SRC has updated the CVE records for CVE-2020-8554, CVE-2020-8561, CVE-2020-8562, and CVE-2021-25740.

26 May 2026 5:30pm GMT

feedJavaScript Weekly

npm and pnpm introduce staged publishing

#​787 - May 26, 2026

Read on the Web

JavaScript Weekly

JS Crossword: All the Answers are JavaScript - This hand-crafted puzzle will seriously stretch your JavaScript knowledge. I've seen so many people on social media either cheering having finished it or cursing being stuck…

Lyra Rebane

💡 I've put some (educational!) tips at the end of this issue.

Expo UI Hits Stable: Native iOS & Android from One Import - From a single import, @expo/ui ships SwiftUI on iOS and Jetpack Compose on Android with the real platform components underneath. SDK 56 also lands native drop-in replacements for seven common React Native community packages.

Expo sponsor

Staged Publishing for npm Packages Goes Live - npm's 'staged publishing' model provides a review period with approval required before packages go live on the npm registry. Both npm 11.15.0 and pnpm 11.3 have added support.

The npm Project

💡 In this broader writeup, GitHub also introduced npm's new --allow-* options to control over where npm is allowed to source packages from.

IN BRIEF:

RELEASES:

📖 Articles and Videos

Chrome Previews Declarative Partial Updates - Two new sets of APIs for working with HTML out-of-order, whether in the doc itself (via <template for>) or through dynamic insertion (via setHTML/streamHTML). Experimental in Chrome 148 but polyfills exist.

Pollard and Rosenthal (Chrome)

Optimizing Our Build Times by Migrating from Webpack to Rspack - How Yelp cut build times in half with Rspack (a Rust-powered drop-in replacement for webpack) and what they learned about barrel files and re-exports.

Benson Pan (Yelp)

Unlimited Postgres for Developers and Their Agents - ghost gives your agent unlimited postgres forks. No project limits, no cleanup, 1TB storage, 100 hrs/mo free. Try for free

Ghost sponsor

Microsoft's Analysis of the Recent Mini Shai-Hulud Compromise - A detailed post-mortem of last week's 'Mini Shai-Hulud' npm security chain compromise.

Microsoft Defender Security Research Team

🤖 AI-Assisted Engineers are Burning Out: Is This Fine? - A look at the negative effects of AI-assisted coding and how to avoid burning yourself out. Ivan Chepurin

📄 A Simple Clustering Algorithm for Lists - Some algorithm fun. Cassidy Williams

🛠 Code & Tools

Deno 2.8: The 'Biggest Minor Release' to Date - The headline is that Node.js compatibility has jumped from 42% in Deno 2.7 to 76.4% now (higher than Bun). Deno also gets huge perf gains across the board and drops the npm: prefix requirement when adding/installing packages. Plus many other things, including:

Bartek Iwańczuk

10 Merged, 34 to Go: Fixing JS Observability Upstream - Every JS APM tool monkey-patches libraries. It breaks with ESM, bundlers, and non-Node runtimes. Here's how to fix it.

Sentry sponsor

📄 DOCX 9.7: Build Word .docx Files in JavaScript - A mature, comprehensive library for generating docx files both client and server side. There's a CodePen-based example with the basics, plus over 100 example scripts.

Dolan Miu

tinykeys 4.0: A Tiny, Modern Library for Keybindings - Has a very simple, straightforward API and the page includes live demos.

Jamie Kyle

An Official Node.js Codemod to Migrate from Axios to fetch - A codemod to transform code using Axios to using the Fetch API instead.

The Node.js Team

📱 Hot Updater: Self-Hosted Over-the-Air Updates for React Native - A way to deploy updates to apps without app store submissions.

Sungyu Kang

📰 Classifieds

🦊 Foxit's open-source MCP server gives AI agents 30+ PDF tools - covering PDF conversion, OCR, merge, signing, and document workflows.

⚙️ Middleware, but for AI agents. Compose Claude Code, Codex & Gemini as one TypeScript harness - 100+ agent recipes. agentfield.ai/github.

Flaky tests slowing down dev? Meticulous gives engineers confidence to ship faster by autonomously testing every edge case of your web app.

👀 JS Crossword Tips

The JS Crossword (featured at the top of the issue) is tough, so I have some educational tips and JS quirks to help you on your way:

  • The crossword runs in the browser, so the window global object is in play. For example: find(0) and name return things in the browser, but not in Node.

  • Look at the 'playground' beneath the puzzle. While a clue may say object, the expected result may be more detailed.

  • A number like 67 can be represented multiple ways. For example: 0103 == 67 and 0x43 == 67

  • You can go further with prefixes and suffixes on numbers. For example: 123., +123, and +123. all equal 123

  • Assignments evaluate to the value that was assigned.

  • Tagged template literals offer a… quirky way to call functions. Consider that this works in JS: console.log`hi` (though this is not equivalent to console.log('hi')).

  • ' is not in the allowed character list.

26 May 2026 12:00am GMT