Kubernetes
Container orchestration
Gateway API takes layer 4 to standard, and Kubernetes moves closer to one networking API.
◆Recent moves
- 8d ago
Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard
⚡ SPARKGateway API v1.6 graduates TCPRoute and UDPRoute to the standard channel, extending an API that previously stopped at HTTP and TLS. This is the networking consolidation thread reaching layer 4 — the same API now describes traffic Ingress was never shaped to handle.
View source ↗ - 11d ago
Kubernetes v1.37 Sneak Peek
The release team's advance notice of deprecations, removals and replacements planned for v1.37. These posts are how the project paces breaking change — required reading before an upgrade, but nothing has shipped in it yet.
View source ↗ - 13d ago
How the controller-runtime Cache Actually Works, and Why Your Controller Does Not Crash the API Server
A community deep-dive into controller-runtime's cache and the informer behaviour behind it, aimed at people whose controllers misbehave once load grows. Educational content rather than a project change, though it reflects how much custom-controller writing the ecosystem now takes for granted.
View source ↗ - 28d ago
Building a Custom Metrics Exporter for Kubernetes
A walkthrough of writing and packaging a custom metrics exporter for the scaling signals CPU and memory do not capture — queue depth, batch duration, open connections. Tutorial content, not a release.
View source ↗ - 29d ago
Operating AI/ML Workloads on Kubernetes: A Headlamp Plugin for Kubeflow
A Headlamp plugin that surfaces Kubeflow's custom resources — notebook servers, training jobs, pipelines — in the same UI as the rest of the cluster. It extends the Headlamp push into AI/ML workloads, which is where recent plugin work has been pointed.
View source ↗ - 29d ago
Kubernetes Dashboard to Headlamp: A Step-by-Step Guide
A migration guide from Kubernetes Dashboard to Headlamp, spelling out the kubeconfig and ServiceAccount differences between desktop and in-cluster operation. Publishing it alongside the plugin announcements makes the succession explicit rather than implied.
View source ↗