Marina UI — the macOS app
A native SwiftUI companion app for the marina CLI. See your VM, kind clusters, and registry mirrors at a glance — live charts and reachability checks, without juggling terminals.
Why
The CLI is great for one-off commands. But to keep an eye on
what's running, how loaded it is, and which LoadBalancer
services are reachable, you'd otherwise be juggling
marina cluster list, kubectl get,
kubectl top, ssh, and
du -sh across a fistful of terminals. Marina UI rolls all
of that into one app.
What it shows
| Panel | What you get |
|---|---|
| Sidebar | marina runs a single VM, so it's pinned at the top; Fleets & Clusters — each cluster with its relative age (e.g. 5h ago), grouped under its fleet — registry mirrors and Docker containers are listed below, each area with its own colour. Refresh everything from the window toolbar or with ⌘R. |
| VM dashboard | Live CPU% and memory graphs, sampled every 5 s over the SSH ControlMaster socket marina already maintains. |
| Cluster creation | Create a cluster from the sidebar's + menu or the New cluster card; it appears immediately with a live, auto-scrolling log of marina cluster create — and any marina warnings (e.g. a non-default kind node version) surface right in the sheet. |
| Fleet creation (v0.5.1) | Create a fleet from the + menu or the New fleet card: a fleet name and the names of its clusters, one per line or comma-separated. The app runs marina fleet create --adopt, so a listed cluster that already exists joins the fleet — see Create a fleet. |
| Per-cluster view | Node + pod inventory, live CPU/memory time series, and top pods by CPU and memory — with one-click Helm install of metrics-server. Hover a pod in the top-pods tables to overlay its history on the cluster charts for side-by-side comparison. The detail header shows the cluster's age. |
| Fleet view (v0.4) | Click a fleet to see its members with status, Kubernetes version, nodes, API port, region/zone, dependsOn, registry mirror selection, addons (detected live, with missing when the manifest enables one that isn't installed) and labels — plus the manifest as syntax-coloured YAML you can copy or save. |
| Workloads (v0.4) | A Workloads tab per cluster: Deployments, StatefulSets, DaemonSets, Jobs and CronJobs with ready x/y, restarts and age, each expandable to its pods. Refreshes every 5 s while visible; filter by namespace, system namespaces hidden by default. Rollout restart and delete pod, both confirmed. |
| Logs (v0.4) | One log viewer for a pod's container (including the previous, crashed instance), a whole workload (every pod and container, prefixed and merged in time order) and the VM's Docker containers: tail size, timestamps, follow, search with highlighting or only matching lines, copy and save. Pod logs come through kubectl logs — the API server and kubelet — so nothing reaches into containerd on the nodes. |
| Update checks (v0.5) | New releases of Marina UI and the marina CLI, every two weeks or on demand, with a one-click upgrade through Homebrew — see Update checks. |
| LoadBalancer service browser | Lists every Service with external IPs, probes each (ip, port) over real TCP, and renders a clickable link when reachable. |
| Registry mirror inspector | Cache disk usage and image count for each mirror in ~/.marina/registry-cache/. |
Create a fleet
The New fleet sheet asks for two things: the fleet name and the clusters that belong to it. Every other option takes marina's defaults, as in a names-only Fleet manifest.
- The app writes the manifest and runs
marina fleet create -f <manifest> --adopt. Clusters are created one after the other, then the fleet view opens. - A listed cluster that already exists is not recreated:
--adoptadds it to the fleet.
Install
The recommended path is the Homebrew cask:
$ brew tap bcollard/marina
$ brew trust --tap bcollard/marina
$ brew install --cask marina-ui
Or download the latest MarinaUI.dmg (or .zip)
from the
Releases
page.
The release build is signed with a Developer ID and notarized, so Gatekeeper opens it without warnings.
Update checks
Since v0.5 Marina UI looks for new releases of itself and of the marina CLI: every two weeks by default (a day, a week or a month in Settings › About › Updates, or off), and on demand with Marina › Check for Updates… or Check now.
- Update now runs Homebrew for you. For the app:
brew upgrade --cask marina-ui, then it relaunches. For the CLI, after a confirmation:marina down,brew upgrade --cask marina,marina up— the VM has to be stopped while the binary is replaced, and it is started again even if the upgrade fails. - Updates always go through Homebrew. It checks the download's
checksum and keeps
brew listaccurate; Gatekeeper checks the notarization. The app never downloads and replaces itself. A copy not installed with Homebrew gets a link to the release page instead. - What the check sends: one request per product to
github.com/bcollard/<repo>/releases/latest, nothing else.
Upgrading Marina UI
From the app: Marina › Check for Updates…, then Update now. By hand, quit the app and pull the newest release the same way you installed it. With Homebrew:
$ brew update
$ brew upgrade --cask marina-ui
$ open -a Marina
Installed from a download instead? Grab the latest
MarinaUI.dmg from the
Releases
page and drag it over the old copy in /Applications.
Share this section directly:
marina.run/docs/marina-ui.html#upgrading.
Marina UI upgrades independently of the marina CLI —
no VM rebuild needed, since the app only reads marina's state.
Requirements
- macOS 14 Sonoma or later.
- A working marina install — at least one VM under
~/.marina/. kubectlandhelmonPATH(marina pulls these in).
How it works
No backend, no daemon, no new state — Marina UI reads from the same sources marina itself uses:
~/.marina/<vm>/(lima.yaml, ssh config, liveness pid) for VM discovery and SSH.- Cluster kubeconfigs via
kubectl. - The Kubernetes
metrics.k8s.ioAPI for cluster metrics. ~/.marina/registry-cache/for cache sizes.
VM stats come from /proc/stat and
/proc/meminfo read over SSH every 5 s. LoadBalancer
reachability is an actual TCP probe (NWConnection) from the
host — not a static CIDR check.
If metrics-server isn't installed in a cluster, the
Metrics tab offers a one-click Helm install
with --set args[0]=--kubelet-insecure-tls (required for
kind's self-signed kubelet).
Build from source
Clone the repo and run ./build.sh — it requires Xcode (for
the Swift 6 toolchain) and swift-bundler:
$ git clone https://github.com/bcollard/marina-ui
$ cd marina-ui
$ ./build.sh
See also
- bcollard/marina-ui — the app's source on GitHub.
- Getting started — bring up the VM and your first cluster.