Docs / Logs and terminals
Logs and terminals
Combined log streams, shells, debug containers, Node shells, port forwards, files and a local terminal.
Logs
Pods, Deployments, StatefulSets, DaemonSets, ReplicaSets, Jobs and Services stream every container of every matching Pod, following new Pods as they start.
Select rows from any lists, across clusters, and press l for one combined, time-ordered stream.
- Search finds, filters or excludes lines, with case and regex options.
- Filter by level, Pod and container. Levels are detected in JSON, logfmt, klog, Logback and Python formats.
- Export the lines shown as text, JSON or CSV.
- Select lines by clicking (Shift-click for a range, Cmd/Ctrl-click to add or remove one, Esc to clear), then copy them or, with the assistant on, Ask AI about them.
When a container writes faster than the view can keep up, Klystiq slows the stream rather than dropping lines, so it may fall behind real time. The view keeps the latest 100,000 lines.
Shell, attach and debug
Shell, attach and debug (an ephemeral container) open in a tab with a real terminal.
Debug a copy… is for a Pod that crashes too fast to look at. Klystiq creates a copy with the same spec but no labels (so no Service sends it traffic), owner or probes. It either keeps the chosen container up with sleep instead of its command, or adds a debug container from another image that shares its processes. Then it opens a shell in it. The copy is deleted when the tab closes, and ends on its own after 12 hours.
Node shell
Node shell, in a Node's actions menu, creates a privileged Pod on that Node in the host's process, network and IPC namespaces, and opens a root shell there. It's confirmed every time. The Pod is labeled as Klystiq's, deleted when the terminal closes, and ends on its own after 12 hours if the app quits first.
Port forwards
Port forwards listen on 127.0.0.1 and pick a ready Pod for each connection, so they keep working through rollouts. You can keep a forward to start again on launch.
Files
A Pod's Files tab browses its containers, downloads files or folders into a folder you pick, and uploads files into the container. It uses the container's own sh and tar, like kubectl cp. Browsing and downloading only read, so read-only contexts allow them; uploading doesn't.
Local terminal
Ctrl+</kbd>, the terminal button on a cluster card, or **Terminal for …** in the command palette opens your own shell on this computer, with kubectl, helm, flux` and other tools pointed at a context and, if you pick one, a namespace.
Klystiq puts a small kubeconfig of its own first in KUBECONFIG. It names the context (cluster and user names only, no credentials), followed by your usual files, so kubectl config use-context and set-context change only that file. Your kubeconfig is never written.
Read-only mode doesn't limit commands typed here; the terminal says so for read-only contexts.