Home / BeaverDeck / Docs / User Guide / Logs and exec

Logs and Exec

Logs and exec sessions open in the bottom dock. Pod logs can search text, filter warning/error lines, follow the tail, refresh manually, and select any regular or init container. When a pod is blocked or crashing during initialization, BeaverDeck selects the active or failing init container by default.

Exec opens an interactive terminal for ready running pods. If a pod has multiple containers, choose the target container in the exec toolbar. Minimal or distroless images may not have an interactive shell; BeaverDeck shows an exec error in that case.

Permissions: pod logs require pods: view; workload logs require workloads: view. Exec requires both pods: view and exec: edit in an allowed namespace. The ServiceAccount also needs Kubernetes pods/log or pods/exec access. See Permissions.