Luxury Yacht is a desktop app for managing Kubernetes clusters | Hacker News Reader

Luxury Yacht is a desktop app for managing Kubernetes clusters

github.com

83 pointsmooreds39 comments

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.

The video is so much better... https://www.youtube.com/shorts/kCPVZwaH7MQ

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.

I never really felt great about Lens. The interface and workflow just never resonated with me. No shade to the crew behind Lens, it’s purely subjective opinion, and I’m sure a lot of people would say I’m wrong.

I like Headlamp. It’s much closer to how I think these kinds of apps should work. Prior to starting work on Luxury Yacht, my favorite app in this category was https://infra.app/ but unfortunately that has seemingly been abandoned.

As far as how they compare… I think they’re all pretty comparable in terms of features. It’s just a question of finding the one that has the UI you like.

I did try to build some stuff into Luxury Yacht that I haven’t seen in other apps, though. There’s an object diff panel, where you can compare two objects (even in different clusters) and it will diff the YAML. I also have a json log parser, that will render json logs as a table so it’s much easier to read. Just small things like that.

Kubernetes Ops person here who opens HeadLamp at start of the day and leaves it open. Lens is much better than HeadLamp IMO but if you are cost sensitive, HeadLamp can probably get you 95% there.

Can you elaborate a little, please? Also, do you use these tools for managed K8s or standard one?

There is also a https://github.com/freelensapp/freelens fork.

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.

I think LY has a great user interface, and I didn't mean to dismiss your amazing work! That's what makes open source great.

I think Headlamp is less know but now that it's part of Kubernetes SIG UI and the kubernetes dashboard is essentially being deprecated, you'll see a lot more headlamp usage in the future imho and I think headlamp can benefit from more awareness and getting more folks involved too!

https://github.com/kubernetes-sigs/headlamp https://thelandsca.pe/2025/05/21/headlamp-now-part-of-the-si...

Oh hey, no worries! I didn't take your post in a bad way. Headlamp is a great project and I honestly can't believe I hadn't heard about it until very recently. I'm glad you're spreading the word about it.

The author must have taken inspiration from Orbstack which is itself a MacOS app for managing containers, VMs and a local Kube cluster. The first image in the README shows they've selected the cluster Orbstack provisions as the one being managed.

I use orbstack but I wouldn’t say it was any inspiration for Luxury Yacht. I was inspired by https://infra.app which was my favorite app for managing k8s resources before it got abandoned.

I've tried to make Headlamp work with GKE/GDC clusters multiple times on macOS but I simply cannot get it working correctly w/gke-gcloud-auth-plugin. Worked out of the box with Luxury Yacht. I do also like the speed of Luxury Yacht!

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

Ah thanks, I’ll figure out why that’s happening because it should be using my git global defaults.

edit: weird, it’s just the one latest commit, all the others are fine.

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.

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.

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.

Trivial to build something that is opinionated and custom to you?

> 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.

Can you elaborate on what you mean by "manage kubeconfig files"? Do you mean how to create them? How to switch between them? Something else?

https://github.com/sunny0826/kubecm

Tested a bunch and this is the one I stuck with, at least until I make my own. Once the entries are all right, I use the dare I say industry standard to switch between them:

https://github.com/ahmetb/kubectx

In addition to the other recommendations, I always suggest Kubie (https://github.com/sbstp/kubie). The nice thing about Kubie is that it spawns a new shell when you select a kubeconfig, meaning selecting a Kubernetes context in one terminal window doesn't clobber what you're doing in another.

Huh for a moment I thought this was a premium version of Yacht (https://github.com/Yacht-sh/Yacht) which provides a web UI to manage Docker containers (Similar to Portainer).

Interesting “built with these tools” to “useful in this way” ratio

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.

I'm not sure what an enterprise version would look like. I don't have any plans to ever charge for the app, so it'll never be "enterprise" in that regard.

I also like k9s! That team created a really great product for people who want to TUI.

Thanks for the compliment on the name. It's been literally the most polarizing thing about the app. More people comment on the name than on anything to do with how the app actually works, lol. I don't know whether that's a good thing or a bad thing. Probably both. :)

I see we have entered the "Gas Town" naming era.

And I though the arbitrary, non-mnemonic, unrelated-to-anything project/app names had got too much ... obviously we're way past that :(

Author here. I know not everybody loves the name. If I was trying to sell it I might be concerned about that. But it's open-source, and I'm not trying to make any money off of it, just trying to give something back to the community.

I was originally trying to name it something serious-sounding and I quickly found out that pretty much everything decent is taken. And even if you can come up with a good name that's not already in use by three other projects, good luck getting a decent domain for it.

I'm also a musician, and I've been through the drama of trying to come up with band names many times in the past. Here's what I've learned: the name matters, but only so much. If people like a band, they're gonna listen no matter how dumb the name is. Do you think Metallica is actually a good name? How about Def Leppard? Lynyrd Skynyrd? The Beatles? Those names are kinda stupid and nobody cares, lol.

Same thing with software. If the product is good, people will use it, and they are not going to care much about the name. I think Luxury Yacht is better than some made-up word that doesn't mean anything but maybe has some vague connection with kubernetes if you squint at it just right, like a magic eye puzzle.

Just my opinion, though. I'm not wrong, and you're not wrong, we just think about things differently, and that's OK!

Personally, I would like the name to be somehow related to the system. When I'm facing a stack of names and icons, make it easy for me.

Names without some connection to the thing are just more difficult. Maybe the name isn't descriptive - you can only have some many versions of ed, edit, edt, vedit, gedit, zed... I'm perfectly happy with puns and jokes - eric can be connected to (monty) python. It's the connection that makes it memorable. Even yacc and grep have some connection to the program.

I've been using Vivaldi browser for a while now, but neither the name nor icon have formed a natural connection to browsing for me. Same with Lazarus (an IDE), no obvious link (worse, it's nothing to do with raised from the dead). But "Bluefish Editor" at least tells me what it does, not a full description, but plenty.

Are there any good open source GUIs for running local docker on desktop?

Rancher Desktop comes to mind. Maybe Podman Desktop https://podman-desktop.io/docs/migrating-from-docker

"Hello, this is Steve from the compliance department. Did your team just use three man-monthes for erm... luxury yacht develompent?"

This could be an vscode extension. No need for an full fledge desktop app.

You could say that about almost anything. There are plenty of people who dont use VSCode so it seems wise to make it a separate app.

Most VSCode extensions are pure slop, to the point where you’re almost certainly better off using any other option for tools where available.

And I don’t mean slop in the new “AI slop” sense of the word, but more “ostensibly supposed to do something specialized but in practice not particularly effective, well documented, or useful”. The entire extension ecosystem is hot garbage.

Reply on news.ycombinator.com