Access a live terminal and stream real-time logs from your pods directly in the browser — no kubectl installation or local kubeconfig required.
Open any pod from Kubernetes → Pods, then click the Logs tab. Logs stream in real time from the pod's stdout/stderr.
| Option | Description |
|---|---|
| Container | Select which container to tail (for multi-container pods) |
| Previous | Show logs from the previous container instance (useful after a crash) |
| Timestamps | Prefix each log line with its RFC3339 timestamp |
| Lines | Number of recent lines to load on open (default: 100) |
| Wrap | Toggle line wrapping for long log lines |
Use the search bar above the log output to filter lines containing a keyword. Matching lines are highlighted and non-matching lines are dimmed.
Click Download to save the current log buffer as a .log file. For large pods, use the line count option to limit the export size.
The terminal is a full PTY session — tab completion, arrow keys, and interactive programs all work normally.
ops0 establishes a WebSocket connection from your browser to the ops0 backend, which proxies the session to the Kubernetes API server (exec endpoint). No inbound ports are required on the cluster — only the existing API server connection that ops0 uses for all cluster operations.
ops0 attempts to open shells in this order:
/bin/bash/bin/shMinimal containers that have neither will not support terminal sessions.
The terminal window automatically resizes as you resize your browser panel. The PTY dimensions are updated in real time so full-screen tools like vim, htop, and less render correctly.
| Limit | Value |
|---|---|
| Idle timeout | 10 minutes of no input |
| Concurrent sessions | Multiple sessions per pod supported |
| Session logging | All terminal activity is recorded in Audit Logs |
All terminal sessions and log access are:
kubernetes_terminal permission)kubernetes_terminal IAM permission. Contact your organization admin if the tab is missing or greyed out.