Repository navigation
v0.0.12
Added
-
Plugins can live one or more to a file in
plugins/beside
plugins.yaml, k9s's snippet directory: every*.yamlthere is merged
withplugins.yamland checked with it, and a name defined in two files
is an error naming both.ui.reactivereloads a change inside it. (#64) -
jumps.yaml, k9s's custom jumps:enterin a view opens another view
filtered by the selected row —labelSelector: com.docker.compose.project=$PROJECT
on containers opens that project's volumes. Values are filled in once and
matched as text; a variable the view's rows do not give is refused at
startup. (#64) -
:xray net,:xray voland:xray imgroot the xray tree at networks,
volumes or images, as k9s's:xray <resource>; container nodes keep every
container key. (#64) -
The header's
CPU/MEMline: the daemon host's CPU and memory in use, from
the CPU/MEM poll's samples and the host's size — no extra daemon call —
colored bythresholds, andn/awith the poll off. (#64) -
Container labels that preset or skip the
shift-fport-forward prompt,
k9s's FastForwards annotations:dockmaster.port-forwards=8080:80
prefills the prompt anddockmaster.auto-port-forwards=8080:80replaces
it with a yes/no confirm. The value is what the prompt takes, optionally
after a k9s-styleservice::. A label that does not parse is reported in
the prompt, and no label starts a forward without a yes (#64). -
The
shift-fprompt takes several forwards, comma-separated
(8080:80,8443:443). -
fon a container opens:pfnarrowed to that container's forwards,
as k9s'sf(#64). -
portForwardAddressinconfig.yaml(k9s's): the address a forward
listens on, an IP orlocalhost, default127.0.0.1. When it is not
loopback theshift-fprompt and confirm warn that the forward is
reachable from the network, and:pfshows the address (#64). -
ctrl-aopens k9s's aliases view (#64): every:command with its other
spellings, and youraliases.yamlentries, markedalias, as a table you
can filter and sort;enterruns the selected one as if typed at the
palette.:aliasesopens the same view (it was a plain-text list of your
aliases). In the:and/barsctrl-ais still start of line. -
ctrl-din the contexts view runsdocker context rm <name>after a
confirm (#64).default, the context dockmaster is connected through and
the docker CLI's current context are refused with the reason;--readonly
refuses it. -
ctrl-don a compose file in:dirrunscompose -f <file> downafter a
confirm (#64);--readonlyrefuses it. -
keepHistoryinhotkeys.yamlnow does what it does in k9s (#64): the
view the hotkey opens goes on top of the current one, soesccomes back. -
overwriteOutputinplugins.yamlnow does what it does in k9s (#64): a
background plugin's first line of output replaces the "done" flash. -
A root shell on the daemon's host, k9s's node shell (#59):
:hostshell
for the daemon on screen — remote contexts and a plain dockerd included —
andson a Docker Desktop, OrbStack or Rancher Desktop row in the
runtimes view. It runs a privileged,--pid=host,--rmhelper that
nsenters PID 1 and starts the host'ssh. The image is
hostShell.imagein config.yaml (defaultalpine:3, pulled if the
daemon lacks it). It always confirms, naming the daemon and the image;
--readonlyand a context'sreadOnlyrefuse it, and so does a
rootless daemon, where it cannot work. Colima and Podman rows keep
their ssh. -
A
VULNcolumn in the images and containers views: each image's last
vulnerability scan, by severity (C2 H5, with medium and low when there
is room), read from a cache of scan results kept by image ID under the
state directory (scans/). Everyvscan is cached; a result older than
imageScans.ttl(a week) is marked with a trailing~, and sorting on
the column orders by severity. Off by default —imageScans.enableturns
it on, orviews.yamlcan nameVULN— andimageScans.backgroundscans
images with no fresh result one at a time while the images view is open.
Changed
iinspects the selected row, aso,dandydo; copying the full
ID moved fromitoI.enteron a ⎈ kind/k3d node opens the pods' containers inside it, as
enteron a node does in k9s;lis still the node's logs andnstill
works. The header's<enter>reads Pods on a node row.ctrl-ais now a dockmaster key: a hotkey or plugin onCtrl-Ais
refused at startup.- A hotkey,
-c,defaultViewor an alias may name a command by any
spelling the palette takes (x,log,h,dumps,screendumps,?);
those were refused as "not a command".
Fixed
?no longer runs off the bottom of a 40-row terminal: it lists keys,
and points atctrl-afor the:commands, which that list already
holds with every spelling. A test now fails when the help frame is
taller than the screen.- With plugins or hotkeys configured, their help columns stack under the
shortest columns instead of widening help past a 120-column screen and
cutting every description (tuikit v0.0.23's help overlay). (#84)
Full Changelog: v0.0.11...v0.0.12