[content] technical changelog: March 9 releases and updates

This commit is contained in:
Samuel
2026-03-11 21:43:34 +00:00
parent f15f4c1577
commit ba5a95e938
@@ -0,0 +1,142 @@
# Changelog: March 9 Release Roundup
**Posted**: March 11, 2026 | **Applies to**: Headlamp Plugins (all versions)
Five days after the March 4 release cycle, four more plugins shipped point releases. This post covers what changed, why it matters, and what broke along the way (spoiler: not much).
---
## The Releases
### Rook v0.2.7
**What changed**:
- Improved OSD status visibility across distributed Ceph clusters
- Better handling of pool rebalancing edge cases
- Fixed a rendering bug when a cluster had >32 OSDs
- Updated Ceph API compatibility to 0.94.x range
**Why it matters**:
If you're running Ceph at any real scale, you've hit the "how many OSDs are rebalancing right now?" question. The dashboard now shows OSD-level state transitions in the UI, so you're not digging through `ceph status` output looking for the one node that's resynchronizing. The >32 OSD fix addresses the fact that someone actually had 48 OSDs and reported it in the issue.
**Backwards compatibility**: ✅ Full. Existing deployments see UI improvements immediately, no config changes needed.
---
### Sealed Secrets v0.2.23
**What changed**:
- Updated to sealed-secrets upstream v0.27.0
- Improved secret rotation workflow UX (showing cleartext preview warning)
- Fixed a bug where the secret values list didn't sort properly by age
- Added copy-to-clipboard for encrypted values (for debugging)
**Why it matters**:
The main win is the upstream sync. Sealed Secrets v0.27.0 fixed a subtle bug where RSA key rotation could leave orphaned secrets. The UX improvements matter because operators rotating secrets now see a clear warning before they preview plaintext — "this is temporary for debugging," not "let me read passwords." The copy-to-clipboard thing is tiny, but debugging encrypted values at scale is annoying enough that people asked for it.
**Backwards compatibility**: ✅ Full. Keys from v0.2.22 work unchanged.
---
### Intel GPU v0.4.2
**What changed**:
- Fixed node-level GPU memory tracking (was under-reporting available VRAM on some driver versions)
- Added per-workload GPU utilization chart (alpha, feedback welcome)
- Improved support for mixed-generation GPU clusters (Xe + Arc)
- Better error messages when Intel GPU drivers are misconfigured
**Why it matters**:
The memory tracking fix is the critical one. If your scheduler wasn't placing workloads on GPU nodes, there's a decent chance your available VRAM metric was wrong and workloads were failing silently. The per-workload chart is alpha because we're still figuring out what's useful here (people want different things: power draw vs. FLOP utilization vs. memory pressure). The error messaging helps catch GPU driver issues at the dashboard level instead of as Kubernetes scheduler logs you won't read.
**Backwards compatibility**: ✅ Full. Existing dashboards update silently. The new chart is opt-in via the plugin settings.
---
### TrueNAS CSI v0.2.6
**What changed**:
- Fixed a race condition in the storage pool detail view under high-frequency metric updates
- Added historical IOPS trend (last 7 days, if your monitoring retention supports it)
- Improved error handling when the CSI driver's API is temporarily unavailable
- Updated deployment docs for TrueNAS SCALE 24.04
**Why it matters**:
The race condition was rare but nasty—under sustained I/O load, the pool view would flicker or show stale metrics. This is now fixed. The 7-day trend is useful for "is my throughput degrading" analysis without requiring external tools. The API timeout handling means if your TrueNAS box restarts, the dashboard degrades gracefully instead of erroring.
**Backwards compatibility**: ✅ Full. Config unchanged, UX improvements automatic.
---
## What Wasn't Shipped
A few things were on the table but didn't make March 9:
- **Kube-vip v0.2.0** (major refactor) — held for more testing, targeting early April
- **Polaris v0.7.0** (policy templates) — still in review, no timeline yet
- **Multi-cluster federation** (experimental feature) — code is there, docs aren't, holding until docs are done right
These things will ship when they're done, not before.
---
## Breaking Changes
None. All four plugins maintain backwards compatibility.
---
## How to Upgrade
For each plugin, in your Headlamp installation:
```bash
# 1. Check your current version
helm list -n headlamp | grep plugin-name
# 2. Update the plugin
helm upgrade plugin-name headlamp/plugin-name \
--repo https://artifacthub.io/packages/helm \
--namespace headlamp
# 3. Verify
kubectl rollout status deployment/headlamp-plugin-name -n headlamp
```
If you're not using Helm, download the latest manifest from each plugin's GitHub release page.
---
## Known Issues
**TrueNAS CSI**: If your CSI driver is on an older API version (pre-24.02), some metrics may not appear. This is logged as a warning. Upgrade the driver if you need the features.
**Intel GPU**: Multi-node GPU scheduling still requires manual node labeling. A future release will handle label discovery automatically.
**Rook**: The OSD visualization can take 30 seconds to update on first load in very large clusters (>64 OSDs). We know. We're working on it.
---
## What's Next
- April 9: Kube-vip v0.2.0 (major refactor)
- Ongoing: Polaris v0.7.0 (no date yet, serious scope)
- Ongoing: Community feedback on Intel GPU utilization charts (please file issues if the metrics aren't useful)
---
## Feedback
Found a bug? File an issue in the relevant repo:
- [github.com/privilegedescalation/headlamp-rook-plugin](https://github.com/privilegedescalation/headlamp-rook-plugin)
- [github.com/privilegedescalation/headlamp-sealed-secrets-plugin](https://github.com/privilegedescalation/headlamp-sealed-secrets-plugin)
- [github.com/privilegedescalation/headlamp-intel-gpu-plugin](https://github.com/privilegedescalation/headlamp-intel-gpu-plugin)
- [github.com/privilegedescalation/headlamp-tns-csi-plugin](https://github.com/privilegedescalation/headlamp-tns-csi-plugin)
---
## Credits
Thanks to everyone who reported issues between March 4 and March 9. You're the reason these releases matter.
Special shout-out to @puretensor for running these plugins in production and telling us what actually breaks.