Terminal & Logs

Interactive shells into pods and nodes, and real-time log streaming.

Pod shell​

Open with right-click → Shell on any pod row (or from the pod's Info window).

• Auto-detects an available shell: tries bash → zsh → sh.
• Terminal emulator is a full PTY (powered by egui_term): colors, cursor, alternate screen, resize.
• Resizes are propagated to the running process (SIGWINCH).
• Multiple shells can run in parallel — each in its own window.
• Terminal title updates track PROMPT_COMMAND / escape sequences.

Multi-container pods​

If a pod has multiple containers, a picker appears first. Select the container to shell into. Pod Info's Containers tab has per-container Shell buttons as a shortcut.

Shell window lifecycle​

• Closes automatically when the shell exits.
• Pressing Esc closes the window only when the terminal is not focused — this protects running sessions. To close, click outside the terminal first, then Esc.

Clipboard​

• Copy: select text with the mouse, then Cmd/Ctrl + C.
• Paste: Cmd/Ctrl + V (passes text to the shell).
• Terminal keyboard handling has priority: while focused, key events go to the pod, not the UI. So things like Ctrl+F reach bash's readline search.

Node shell​

Right-click → Shell on any node.

Kubezilla creates a temporary privileged debug pod on the node:

• Image: busybox:latest.
• Host root mounted at /host, hostPID: true, privileged security context.
• Pod is placed in the default namespace with restartPolicy: Never.
• Pod is automatically cleaned up when the shell window closes.

Typical usage once inside:

chroot /host

…gives you a root shell on the node itself.

Log streaming​

Right-click → Logs on a pod (or on any resource with pods — Deployment, StatefulSet, etc.).

• Streams in real time (--follow).
• Auto-scrolls to the tail; scroll up to pause auto-scroll, scroll back to resume.
• Logs window stays open when the stream ends (unlike Shell). Close manually.

Multi-container pods​

A dropdown at the top of the Log window lets you switch containers without closing the window. The first container is auto-selected.

Log controls​

Logs from Helm / ArgoCD managed resources​

Helm release Info and ArgoCD Application Info both have a Resources tab. Each managed workload row has a Logs button — opens the Log window scoped to that pod (multi-container picker when needed).

Same for Shell on running pods in those tabs.

Search​

• Log search is always case-insensitive.
• Shell uses Ctrl + Shift + F (leaves Ctrl+F free for the running program).