helm in an unusual place.
Lumovi reads them once, when it starts. Restart it after changing one.
This page is about the desktop app. Lumovi in your cluster has its own settings, set through the Helm chart: see Configuration.
Variables
Where your clusters come from, as for
kubectl. List several files separated by : (; on Windows), and Lumovi merges them the way kubectl does: the first file to define a name wins, and so does the first current-context. Files that are missing or empty are skipped, and relative paths in a file are read from that file’s folder. See Connecting clusters. Each terminal gets these files too, after a kubeconfig of its own. Files chosen in Lumovi take their place, and files added there come after them.On macOS and Linux, the shell terminals start, and the one Lumovi asks for your
PATH. Without it, terminals start zsh on macOS and bash on Linux. On Windows, they start Windows PowerShell whatever it says.Makes every cluster read-only, whatever is set in the app. The read-only switch then reads Set by LUMOVI_READ_ONLY and can’t be turned off. The app’s main process enforces it, not just the buttons, and it covers shells, node shells and Helm too. It doesn’t reach terminals, which are your own shell. Useful on shared machines. Only
1 and true turn it on: anything else, like yes or TRUE, leaves changes on. See Read-only mode.The most one copy of files to or from a container carries: a whole number of bytes, or
off, which turns copying off. With anything else, Lumovi copies nothing until it’s put right. Your organization’s policy wins over it.The proxy Lumovi goes through for
https and http addresses, and what it reaches directly, as kubectl and helm read them, in upper case or lower case. A proxy without a scheme is taken as http://; one that isn’t a URL is left out, and Lumovi says so as it starts, in a notice. On macOS and Linux, Lumovi takes them from your login shell, when they aren’t set where it starts. Your clusters, Helm repositories and Artifact Hub go through it; localhost, 127.0.0.1 and ::1 never do. Your organization’s policy can set the proxy instead. See Proxies and certificates.Where terminals’ matching kubectl comes from: a mirror of dl.k8s.io, laid out as it is (
release/stable-1.34.txt, release/v1.34.9/bin/darwin/arm64/kubectl and its .sha256, and Kubernetes’ .sig and .cert beside it, if the mirror keeps them). Where it keeps them, the kubectl is checked against Kubernetes’ signature, as dl.k8s.io’s is; where it doesn’t, against the mirror’s checksum only, and each terminal says so. It must be https, or on this computer (localhost, 127.0.0.1 or [::1]): otherwise terminals use the kubectl on your PATH, and say why: “Lumovi gets kubectl only over HTTPS, and http://mirror.corp.example.com/ isn’t (LUMOVI_KUBECTL_MIRROR)”, without any user and password the URL has. Empty, it’s as if it weren’t set. Your organization’s policy names one instead, when it does, and can require Kubernetes’ signature from either (kubectlSignatures): a kubectl the mirror keeps none for then isn’t used.A policy file to try out, where your computer has none. Where IT has set one, in the system’s file or, on Windows, the registry, that one is used, and this is ignored.
The most objects a list loads. Lists are fetched in chunks of 500 and stop here, with a note saying so. Filter by label to see the rest, or raise the limit for a very large cluster. A value that isn’t a number leaves the default.
How long the API server has to answer a request. Raise it for a slow or distant API server that shows The cluster isn’t responding. A value that isn’t a number leaves the default.
Where your own plugins are. Every
.yaml and .yml file directly in it is read, up to 200 files of at most 256 KB each. Folders inside it aren’t, except, in the desktop app, a plugin with code: <name>/plugin.yaml and its plugin.js.Another
helm to run when you change a Helm release. Without it, Lumovi runs the helm it ships with: helm 4.3.0, the same as its image’s. Run from source, with npm run dev, it has none, and runs the helm on your login shell’s PATH. See Which helm runs.The Artifact Hub to search when you install a chart.
You don’t need to set
PATH for credential plugins, or your proxy. On macOS and Linux, apps opened from the Dock or a launcher don’t see what your shell sets up, so Lumovi asks your login shell for its PATH, HTTPS_PROXY, HTTP_PROXY and NO_PROXY when it starts. That’s how gke-gcloud-auth-plugin, aws, kubelogin and helm are found, and your clusters reached through the proxy. Other variables aren’t read from your shell profile: set them as below.Setting them
- macOS
- Linux
- Windows
Quit Lumovi first. Then start it from Terminal with the variables in front of the command:Apps started with This lasts until you log out or restart.
open get the environment of the shell that ran it. If Lumovi is already running, open brings that copy to the front instead, without the new settings.To have every launch from the Dock or Spotlight pick a variable up, set it for your session:launchctl unsetenv LUMOVI_READ_ONLY removes it.