views value, one entry per file name:
values.yaml
.yaml or .yml at the end, with one or more views and add-ons separated by ---, exactly as you’d write them for the desktop app. See Write a view, Add-ons and the view format.
How it works
- The chart puts the files in a ConfigMap, and mounts it at
/etc/lumovi/views, where Lumovi reads them (LUMOVI_VIEWS_DIR). - A view of a kind replaces Lumovi’s own view of that kind, one kind at a time.
- An add-on replaces Lumovi’s add-on with the same name, like
fluxorcert-manager. - A change to
viewsrolls out a new pod, which reads them. That signs everyone out, as any restart does. - Views and add-ons are the server’s, for everyone. People can’t add their own from a browser.
Check them
API resources (in the sidebar, or ⌘K, CtrlK on Windows and Linux) shows which view each kind uses, and lists anything wrong with the views and add-ons. One with a problem isn’t used at all, and the problem says where it is. At the bottom, it says how many views come from Lumovi and how many from this server, and where they are, like 101 views from Lumovi, 2 from this server. This server’s are in /etc/lumovi/views. Views are data only. They read fields with JSONPath, and change objects only with the patches and new objects they spell out. Their actions go through the same checks as Lumovi’s own: the cluster is asked first whether the person may make the change, the equivalentkubectl command is shown, and a read-only Lumovi stays read-only.
Write a view
A step-by-step guide, from columns to actions.
View format
Every field a view or an add-on can have.