Normalize a Kubernetes runtime support bundle locally, identify CrashLoopBackOff, ImagePullBackOff, OOMKilled, FailedScheduling, probe and dependency failures, then generate a timeline and read-only commands.
Resources: 10 MiB and 5,000 objects. Describe and logs: 5 MiB each, with up to 50,000 log lines.
Pods, containers, Events, an incident timeline, diagnostics and read-only troubleshooting commands will appear here.
Offline analysis cannot observe live state, controller behavior, network dataplane or cloud-provider events and does not replace in-cluster diagnostics.
Analyze Pods, Events, describe output and container logs together. Normalize a Kubernetes runtime support bundle locally, identify CrashLoopBackOff, ImagePullBackOff, OOMKilled, FailedScheduling, probe and dependency failures, then generate a timeline and read-only commands. The core workflow is designed to run in your current browser.
Yes. Kubernetes Runtime Diagnostics Analyzer opens in a modern browser and does not require desktop software installation.
Common use cases include Quickly triage Pending, CrashLoopBackOff and OOMKilled workloads; Explain FailedScheduling, resource pressure, taints and PVC problems.
The core processing workflow is designed to run locally in the browser. Key capabilities include Read Pods, Lists, Events, Nodes, PVCs, describe output and logs, Identify common startup, image, memory, scheduling, volume and probe failures, Combine Events and container termination states into an incident timeline; account, comments, and anonymous analytics may still create normal site requests.
0 comments
Sign in to comment and reply.
