feat(logs): right-click a deployment's pod → View Logs (HELM-102) - #59
Merged
Conversation
Add a "View Logs" item to the right-click menu on pod rows in the Related
resources list (shown in the expanded Deployment/StatefulSet/DaemonSet/
Service/Ingress/Job detail). It routes to /logs and hands the target pod to
the Logs panel via the existing focusRequest mechanism, which switches to the
Pods kind, auto-selects the pod, and starts streaming with no further clicks.
Namespace is preserved; container defaults to all and stays switchable.
- resourceNav: goToPodLogs() helper (navigate /logs + set a ns/name-keyed
{kind:pod} focusRequest — ns/name, not uid, so the Logs sidebar can match it)
- RelatedResources: wrap pod rows in a context menu with View Logs
- LogsPanel: consume the incoming pod focusRequest and select/stream the pod
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Generalize the pod "View Logs" affordance to workloads. A deployment row's
context menu gets a "View Logs" item that opens the Logs panel streaming that
deployment (all its pods, by label selector).
- resourceNav: goToPodLogs → goToLogs({ kind, namespace, name }), where kind is
pod | deployment | statefulset | daemonset
- LogsPanel: consumer maps the focusRequest kind → sidebar LogKind, so it opens
under the right tab (Pods for a pod, Deploy for a deployment) and streams
- DeploymentRow: add "View Logs" to the row menu
- RelatedResources: pod rows now call goToLogs({ kind: "pod", ... })
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HELM-102
From the Deployment panel, right-click one of a deployment's pods and choose View Logs to jump straight to the Logs panel with that pod's logs already streaming — no manual navigation or pod selection.
What changed
resourceNav.goToPodLogs(navigate, pod)— reusable helper that navigates to/logsand sets a{ route: "/logs", kind: "pod", key: "ns/name" }focus request. Usesnamespace/name(not uid) so the Logs sidebar — which keys its rows byns/name— can resolve it. (/logsisn't inNAV_META, sogoToResourcecan't do this.)RelatedResources— pod rows (the pod list shown in an expanded Deployment/StatefulSet/DaemonSet/Service/Ingress/Job detail) now have a right-click context menu with View Logs. Non-pod andmissingrows are unchanged.LogsPanel— consumes an incoming pod focus request: switches to the Pods kind, clears any sidebar search, and auto-selects + streams the target pod once the Pods watch delivers its row.Acceptance criteria
/logsand auto-selects the exact podVerification
pnpm --filter web typecheck✅pnpm --filter web test✅ (1724 tests; +2 new forgoToPodLogs)pnpm --filter web build✅🤖 Generated with Claude Code