Skip to content

feat(kubernetes): refresh resource details and stream workload logs - #389

Merged
hoalongnatsu merged 2 commits into
mainfrom
feat/kubernetes-harness
Oct 23, 2026
Merged

hoalongnatsu merged 2 commits into
mainfrom
feat/kubernetes-harness

Conversation

@hoalongnatsu

Copy link
Copy Markdown
Member

What does this PR do?

Redesigns Kubernetes resource details around health, evidence and live logs, with
a consistent desktop and mobile experience. Deployment and StatefulSet logs now
follow their Pods together in one viewer instead of requiring repeated snapshot
refreshes.

  • Resource overview: readiness, restarts, uptime, CPU and memory tiles,
    available usage history, conditions and a compact live-log view.
  • Live workload logs: All pods by default, coloured Pod prefixes, Pod and
    container selection, filtering, timestamps, wrapping and download of retained
    lines. Newly discovered Pods join the stream during rollouts and scaling.
  • Previous logs: inspect available previous-container output as a finite
    read, clearly separate from a live tail.
  • Focused detail tabs: grouped Events with activity history; searchable,
    foldable, read-only projected YAML; a relationship map; and resource Timeline
    changes and crash evidence.
  • Reliable investigation: preserve the log session when moving between
    Overview and Logs, resume across stream rotation, and recover automatically
    from temporary stream-capacity errors during rapid control changes.
  • Less clutter: captured crashes use a compact summary with optional details.
    Capture settings no longer list machine-facing size limits. Agent learning
    moves to the bottom and remains disabled because it is not implemented.

Why?

Investigating a Kubernetes failure should not require switching between separate
resource views or opening each replica's logs. This brings the important context
and arriving log output together, while keeping the interface simple enough to
use during an incident.

Type of change

  • Bug fix (non-breaking)
  • New feature (non-breaking)
  • Breaking change (config / API / default behavior)
  • Documentation only
  • Refactor (no functional change)
  • CI / build / chore

Checklist

  • go test ./... passes locally
  • go vet ./... is clean
  • Added or updated tests for the change
  • Updated user-facing docs under src/ if behavior changes
  • Updated ROADMAP.md if this closes a roadmap item
  • No secrets, tokens, or webhook URLs introduced in source / YAML
  • No new third-party dependencies (or justified in the description)

@hoalongnatsu
hoalongnatsu merged commit 302a31d into main Oct 23, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant