19 comments

[ 2.8 ms ] story [ 40.5 ms ] thread
For those who don't know https://headlamp.dev already exists and is in CNCF.
How does this compare to LENS? https://lenshq.io/

Always used the free and paid version and never heard of headlamp. Having a look its basically the same but for free.

Hey there. I didn’t submit this post but I am the author of the app. I didn’t know about Headlamp when I started working on Luxury Yacht. I only discovered it a few weeks ago. Headlamp is great, and of course having CNCF’s backing means a lot.

I’m not trying to sell Luxury Yacht. It’s free to use. I’m not going to try to convince anyone to choose it over Headlamp, or any other tool. Of course I’m flattered if people like what I built, but that’s the extent of my investment.

I like Luxury Yacht better than Headlamp, but of course I do, because I built it to work exactly the way I want it to.

Interesting “built with these tools” to “useful in this way” ratio
BTW it's pronounced 'Throatwobbler Mangrove'

(http://montypython.50webs.com/scripts/Series_2/43.htm)

Author of the app here. That’s one of the reasons I picked the name. When I was trying to come up with a name for this thing, I didn’t want another “k” name, but I did want something that tied in with the nautical theme of kubernetes. Luxury Yacht ticked that box and the Monty Python connection was a sweet bonus.
(comment deleted)
This could be an vscode extension. No need for an full fledge desktop app.
Just as a heads up to the author, some of the commits against Luxury Yacht aren’t attributed to a GitHub account because Git wasn’t configured to use an email that’s associated —

https://github.com/luxury-yacht/app/commit/62953f68b94e55259...

  From 62953f68b94e552596a149474c632c0ea0a05bf3 Mon Sep 17 00:00:00 2001
  From: John Jeffers <john@jbook-fusionauth.localdomain>
  Date: Thu, 15 Jan 2026 21:07:51 -0700
  Subject: [PATCH] add linux troubleshooting info
These days I just write specific TUIs for my infra. Claude can do it with Ratatui in no time. You can make it specific to your preferences. Like I press j to go to jobs. And hit l for logs that are then auto refreshed or whatever. Who knows what other people want. I just make for me and it rules. You can then mix infra and application handling in the same TUI. Press c for the per-customer infra selector. Not useful to anyone but people here.

Trivial to build.

EDIT: Yes, to responder. Trivial to build for me. Don’t need more users. Just make for yourself.

> Luxury Yacht reads your .kube directory and loads your existing kubeconfig files. It does not create kubeconfig files, nor will it ever modify them in any way. It's up to you to get those working correctly for your clusters.

I'm wondering if the author or anyone else familiar could suggest some good tools to help manage kubeconfig files. I don't have this problem using Rancher for example, and it's a big reason why I've struggled with K9s and OpenLens.

"Hello, this is Steve from the compliance department. Did your team just use three man-monthes for erm... luxury yacht develompent?"
Are there any good open source GUIs for running local docker on desktop?
If theres ever launch an enterprise version, I'll push for this product to be adopted across the company. And what a phenomenal name. Also a huge fan of k9s myself.
A native desktop UI for Kubernetes is an interesting angle, especially as clusters get more complex and distributed. Most existing tools lean heavily on CLIs, browser based dashboards, or cloud specific consoles, which can make cross cluster visibility and day to day ops harder than it needs to be. The key questions for me are how well this handles scale, RBAC, and multi cluster workflows, and whether it meaningfully reduces cognitive load compared to kubectl + existing dashboards. If it does, there’s real value here beyond just being a nicer UI.
Desktop Kubernetes tooling like this is an interesting counterpoint to the “everything is CLI” philosophy. For teams managing multiple clusters and contexts, a well designed desktop app can surface state, resource relationships, and misconfigurations much faster than stitching together kubectl, plugins, and ad-hoc scripts. The value isn’t replacing the CLI, but reducing cognitive load for common workflows like context switching, inspecting workloads, and debugging cluster health. The key questions are how well it integrates with existing auth flows (RBAC, cloud IAM), whether it stays performant on large clusters, and how transparent it is about the underlying API operations. If it avoids becoming a leaky abstraction, this could be genuinely useful for day to day cluster management.