kuno
A terminal UI for Kubernetes, focused on the parts of cluster work that happen most often: finding a resource, tailing its logs, reading a manifest or describe output, checking events. Everything is keyboard-driven and fast.
Requirements
- uv
- A valid kubeconfig
Install
uv tool install kuno
If you don't have uv:
curl -LsSf https://astral.sh/uv/install.sh | sh
uv tool install kuno
kuno requires Python 3.11+ and uses
match/casesyntax. If your system Python is older,uv tool installautomatically downloads a compatible interpreter.
Then run:
kuno
To update:
uv tool upgrade kuno
Install from source
git clone https://github.com/1cadumagalhaes/kuno
cd kuno
uv sync
uv run python -m kuno
Usage
kuno [-c CONTEXT] [-n NAMESPACE] [-d]
| flag | description |
|---|---|
-c, --context |
Kubernetes context to use (overrides config default) |
-n, --ns, --namespace |
Namespace to use (overrides config default) |
-d, --debug |
Write debug output to /tmp/kuno_debug.log |
Navigation
j / k or arrow keys move through the resource list. g / G jump to top and bottom.
Press : to open the command bar, or ctrl+p for the Textual system command palette.
Key Bindings (main explorer)
| Key | Action |
|---|---|
j / k or arrows |
Navigate list |
g / G |
Jump top / bottom |
Enter |
Drill into selected resource |
d |
Describe selected resource |
i |
Toggle Info side panel |
y |
View YAML manifest |
r |
Refresh current view |
L or l |
Open Logs for selected resource |
C |
Jump to Contexts view |
N |
Jump to Namespaces view |
ctrl+d |
Delete selected resource (with confirmation) |
ctrl+r |
Restart selected deployment/statefulset (with confirmation) |
ctrl+x |
Clear failed pods in current namespace (with confirmation) |
ctrl+e |
View Events |
ctrl+o |
Sort cycle |
Backspace |
Go back |
? |
Show all keybindings |
: |
Open command bar |
ctrl+p |
Textual system command palette |
: Commands
| command | description |
|---|---|
:pods / :containers |
switch to pods / containers |
:deploy / :deployments |
switch to deployments view |
:sts / :statefulsets |
switch to statefulsets view |
:svc / :services |
switch to services view |
:pvc |
switch to PVC view |
:secrets |
switch to secrets view |
:contexts |
switch to contexts view |
:namespaces / :ns [name] / :namespace [name] |
switch or set namespace |
:ctx <name> |
switch context |
:logs |
open logs for selected resource |
:yaml |
view raw manifest |
:describe |
describe output with inline events |
:events |
view events |
:del / :delete |
delete selected resource (with confirmation) |
:restart |
rollout restart selected resource (with confirmation) |
:clear-failed / :clear-succeeded / :clear-evicted |
delete all pods in a terminal state for the current namespace (with confirmation) |
:info / :hide-info |
toggle the info side panel |
:config |
open config screen |
:theme [name] |
cycle or set theme |
:help |
show this command list |
Logs Screen
| Key | Action |
|---|---|
y / ctrl+c |
Copy text selection (if any) |
d |
Open log detail panel |
f |
Toggle follow mode |
j / k |
Previous / next line |
g / G |
Jump to top / bottom |
/ |
Focus filter input |
s |
Focus since (time) input |
t |
Toggle timestamps |
w |
Toggle line wrapping |
m |
Cycle display mode (raw / structured) |
r |
Reload logs |
ctrl+u |
Clear filter |
n / N |
Cycle search matches |
[ / ] |
Previous / next pod (workload views) |
ctrl+h / ctrl+l |
Previous / next container |
Manifest / Describe Screens
/ toggles search. [ and ] jump between YAML keys at any nesting level.
Configuration
kuno reads from ~/.config/kuno/config.toml on startup and writes back when you save from :config.
[ui]
theme = "nord"
yaml_theme = "monokai"
[logs]
wrap = false
timestamps = false
mode = "raw" # raw or structured
tail_lines = 500
[defaults]
# context = "my-context"
# namespace = "default"
theme accepts any Textual built-in theme. yaml_theme accepts any Pygments style name.
kuno remembers the last namespace you used per context (stored in ~/.cache/kuno/state.json), so switching back to a context restores the namespace you had selected.
Development
uv sync
make test
make check # format + lint + typecheck + tests
make run # run against current kubeconfig
To target a specific context or namespace during development:
make run CTX=my-context NS=my-namespace
Metadata
Release files for kuno 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kuno-0.2.2.tar.gz | 57.3 kB | With provenance | Details for kuno-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kuno-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for kuno-0.2.2-py3-none-any.whl |
Total release size: 119.0 kB
Release files / kuno-0.2.2.tar.gz
| Download URL | kuno-0.2.2.tar.gz |
|---|---|
| Size | 57.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cde37bd9b53f5172d0448fc99965b7393f4d545749ea68709459ea669cac13a3
|
|
BLAKE2b-256 checksum How to use checksums |
c28f33e3809856d7ae0f2c3f850f6249c595d8b52ddd09f6a1d3b9bf1645ab83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logRelease files / kuno-0.2.2-py3-none-any.whl
| Download URL | kuno-0.2.2-py3-none-any.whl |
|---|---|
| Size | 61.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ccdf52840ab33bbc7002b6ba08cf0c16c3175a5697fc12b5977987c97a1c2793
|
|
BLAKE2b-256 checksum How to use checksums |
aaac2db7f65c4443cbfae2f538a34a5b2d5c5e739e7eec86d0a8c1fc708de1d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logSecurity for kuno 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for kuno-0.2.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.