Kubernetes Dashboard is archived. Lens is a subscription. Between those two, one project ended up as the answer to both - which made this week's Showdown block write itself. That's the shape underneath all four of these: something that looked settled - a boundary, a standard, a free tool, a security model - turning out to hold less than advertised.
Grab bag, round two.
🚀 Sandbox Watch: Gonzo
What it is
A terminal log viewer built specifically for OTLP, from ControlTheory, a small observability startup. It surfaced publicly around KubeCon 2025 USA, MIT licensed, sitting around 2,800 GitHub stars now.
How it works
Built on Bubble Tea, Charm's TUI framework - not the tview/tcell stack k9s runs on. "Inspired by k9s" means the 2x2 grid layout and vim-style keybindings, not shared code. It runs its own OTLP receiver - gRPC on 4317, HTTP on 4318 - so logs land directly, no Loki or Elasticsearch sitting in between. It also auto-detects JSON, logfmt, and plain text, with prebuilt integrations for Kubernetes pod logs, Docker, syslog, and a long list of platforms: Vercel, Supabase, Railway, Cloudflare Workers, Netlify, Fly.io, Render, AWS CloudWatch.
The honest part
A Show HN commenter reported 5,000 log lines taking over six minutes to process on their machine - "so slow" was the exact complaint. Worth checking against your own log volume before you commit to it. There's also a fixed bug about returning terminal control to the parent process "(e.g. k9s)" on quit, which tells you people are already running this as a k9s plugin rather than standalone.
And it isn't purely a community project. Gonzo shares a blog and a company with ControlTheory's paid product, an AI-focused observability platform pitched right alongside it. That doesn't make the free tool worse - it's still MIT, still yours to run - but it's worth knowing you're also looking at a funnel.
Links
💎 The Hidden Gem: CloudEvents
What it is
The CNCF's standard envelope for events - not a message bus, not a delivery protocol, just an agreed shape for "here's what happened." Spec v1.0.2, Graduated in the CNCF in January 2024, health score rated "Excellent." Google, Microsoft, IBM, Red Hat, VMware, SAP, and Serverless Inc. all had a hand in it - a vendor consortium, not one inventor.
The envelope
Four required fields: id, source, specversion, type. A handful of optional ones: datacontenttype, dataschema, subject, time. That's genuinely it - small enough to hold in your head, which is the whole point.
Who actually uses it
Knative Eventing is the deepest integration - Broker and Trigger are built directly around CloudEvents. Dapr wraps pub/sub messages in a CloudEvents envelope by default. AWS EventBridge and Azure Event Grid both support it too, but as an opt-in mode through API Destinations or a schema setting - not what you get by default.
Where it stops helping
The spec doesn't touch routing or delivery guarantees - that's left entirely to whatever's actually moving the event around. And dataschema is optional, which means the envelope is standardized but the payload inside it usually isn't. A consumer still can't validate a CloudEvent's actual data without a separate, out-of-band agreement on what that data looks like. CloudEvents solves "what shape is this event," not "what does it mean" or "will it arrive."
Links
⚔️ The Showdown: Lens went paid, Kubernetes Dashboard went dark, one project answers both
The setup
Mirantis has been tightening Lens's licensing since 2023 - marketplace extensions gated, multi-cluster limited, an Enterprise tier added in 2024. Since October 1, 2024, even the free Personal plan lost team features - shared clusters and Spaces now need a Pro or Enterprise subscription.
The one everyone still recommends, and shouldn't
OpenLens - the open-source fork people reach for reflexively - is dead. Last release was v6.5.2 in June 2023. No cease-and-desist, no drama: once Mirantis stopped shipping an open core to fork from, contributions simply stopped. If a "just use OpenLens" comment is more than a year old, don't trust it.
What's actually alive
FreeLens is the real successor - a fresh community fork started in 2024/2025, sitting around 5,300 stars, cross-platform, no proprietary licensing anywhere in it. If you want the original Lens desktop experience without a subscription, this is it now, not OpenLens.
The other half of the story
Kubernetes Dashboard - the official web UI - was archived on January 21, 2026. The repo is read-only. And the project's own farewell note points people toward Headlamp.
Headlamp has been CNCF Sandbox since May 2023, with Microsoft engineers (formerly Kinvolk) actively maintaining it, a monthly release cadence, and both web and desktop builds behind a plugin system. It's the one project that both halves of this story - the paywalled desktop app and the abandoned official dashboard - now point toward.
My read
Terminal-first: k9s, untouched by any of this. Want the original Lens desktop feel for free: FreeLens. Want the option positioned to be the default going forward, with a real team behind it and a plugin ecosystem: Headlamp. Kubernetes Dashboard has dropped out of the running entirely - it's the cautionary footnote now, not a fourth option.
Links
👮 The Policy: the container isn't the boundary that matters
The framework, and where it comes from
"Boundary, Policy, Lifecycle" as three separate questions for AI-agent sandboxing isn't an industry standard - it's from a single blog post by Luis Cardoso, a malware-analysis researcher, published in January. Worth saying plainly, because backlog notes and secondhand summaries have a way of making a good personal framework sound like consensus. It isn't, yet. But it's a genuinely useful way to cut the problem, and this year handed it a lot of supporting evidence.
What it says
Three separate questions, and most sandbox security effort only answers the first. Boundary: can the code physically escape the container, VM, or process? Policy: even fully inside the boundary, what is the agent actually allowed to touch - credentials, network egress, the host filesystem through a mount? Lifecycle: what happens to that access after the task that needed it ends? Most engineering attention goes to boundary. Most real incidents turn out to be policy.
The week that proved it
In July, security researchers documented a string of sandbox escapes across Cursor, Codex CLI, Gemini CLI, Antigravity, and Claude Code - written up as "the week of sandbox escapes." None of them were a broken container boundary. Every one had the same shape: an agent, still fully inside its sandbox, writes a file the boundary was never designed to police - a .vscode task config, a .claude hook, a modified Python virtualenv, git metadata under a nonstandard directory name that slips past path-based rules. Something outside the sandbox later reads and executes that file, unsandboxed. CVE-2026-35603 and CVE-2026-48124 came out of that wave. Anthropic fixed its case quickly; the write-ups describe the other vendors moving slower.
Why the framing matters
The container held in every one of these. Nobody broke out. The failure sat entirely in the second question - policy - which most teams never separately audit, because "we sandboxed it" already feels like the finished sentence.
What to actually check
Not "can the agent escape." Ask what it can still write to, reach over the network, or leave behind after the task ends, even while fully contained. That's three separate audits, not one.
Links
Four different kinds of "that wasn't actually solid." A dashboard that just stopped existing. A standard that only settles the envelope, not the substance. A free tool that's also a sales funnel, which is fine as long as you know it going in. And a sandbox that held perfectly while the policy around it didn't.
The last one is worth sitting with longer than a headline allows. Five different AI coding tools hit the identical failure shape in the same month, and the container was never the part that broke.
Questions? Feedback? Reply to this email. I actually read them.
- Ilia