Repository navigation
feat(kubernetes): refresh resource details and stream workload logs - #389
Merged
Merged
Conversation
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
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.
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.
available usage history, conditions and a compact live-log view.
container selection, filtering, timestamps, wrapping and download of retained
lines. Newly discovered Pods join the stream during rollouts and scaling.
read, clearly separate from a live tail.
foldable, read-only projected YAML; a relationship map; and resource Timeline
changes and crash evidence.
Overview and Logs, resume across stream rotation, and recover automatically
from temporary stream-capacity errors during rapid control changes.
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
Checklist
go test ./...passes locallygo vet ./...is cleansrc/if behavior changesROADMAP.mdif this closes a roadmap item