> 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.
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 <[email protected]>
Date: Thu, 15 Jan 2026 21:07:51 -0700
Subject: [PATCH] add linux troubleshooting infoI see we have entered the "Gas Town" naming era.
Interesting “built with these tools” to “useful in this way” ratio
"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?
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.
This could be an vscode extension. No need for an full fledge desktop app.
For those who don't know https://headlamp.dev already exists and is in CNCF.