Skip to main content
← Back to list
01Issue
FeatureOpenExtensionsPublic
AssigneesNone

Relationships

#4161 deployment: getLogs method (deployment-aware pod log tailing)

Opened by franksolli · 10/30/2026

Requesting a getLogs method on the @swamp/kubernetes/deployment type.

Problem: fetching logs for deployment-managed workloads requires an exact pod name, so callers must first resolve pod names (e.g. kubectl get pods -l / the deployment's pod-template labels). The deployment type has no log method and no pod-discovery capability, while pod.getLogs exists but is name-only.

Suggested method: deployment.getLogs(deploymentName, namespace?, container?, tailLines?=100, previous?=false) that resolves the deployment's current pod from spec.template.metadata.labels (fallback spec.selector.matchLabels), prefers Ready/newest pods, and tails the log via the K8s API — same global-args contract (context/kubeconfig/namespace) as the other methods.

Workaround in the meantime: community extension @franksolli/k8s-deployment-logs (extends @swamp/kubernetes/deployment with exactly this method) — happy to submit it as a PR if useful.

Upstream repository: https://github.com/swamp-club/swamp-extensions

Environment

  • Extension: @swamp/kubernetes@2026.10.25.2
  • swamp: 20261027.172645.0-sha.be9fd9d6
  • OS: linux (x86_64)
  • Deno: 2.9.8
  • Shell: /bin/zsh
02Bog Flow
◉OPEN○TRIAGED○IN PROGRESS○SHIPPED

Open

10/30/2026, 8:17:46 AM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

system commented 10/30/2026, 8:17:46 AM

Classified automatically when this issue was filed.

  • Source: Extensions

If you feel this classification is incorrect, add a ripple to tell us so.

Sign in to post a ripple.