Skip to content
TextArray1.41.0
100% local

Kubernetes manifest overview

Summarize the resources, images and settings in a Kubernetes YAML manifest.

Input
Output
Related tools
YAML ⇄ JSON converterDeveloper tools
YAML formatterDeveloper tools
TOML to JSON converterDeveloper tools
i18n key diffDeveloper tools
SQL to JSONDeveloper tools
JSON Schema validatorDeveloper tools
Kubernetes manifest overview
Paste a Kubernetes manifest — one document or a multi-document YAML stream separated by "---" — and this tool lists every resource it finds: kind, name, namespace and the settings that matter most when reviewing a deployment. Use it to sanity-check a manifest before applying it, to review a colleague's pull request, or to inventory what a Helm template or kustomize build actually renders, without switching to a terminal and running kubectl.
The options set how much detail each row carries. "Show container images and tags" lists what each container in a Deployment, StatefulSet, DaemonSet, Job, CronJob or bare Pod runs, init containers included. "Show resource requests and limits" prints each container's CPU and memory values, so a workload with none set stands out. "Show ports and volumes" adds container ports and the pod's volumes with their type. "Show ConfigMap / Secret references" collects every reference a pod depends on, from env, envFrom and mounted volumes alike. Turn on warnings and a "latest" (or untagged) image or a missing limit gets flagged — two of the most common review comments. Filter by kind or namespace with a comma-separated list, and choose table, list or CSV depending on the use.
The parser accepts real-world YAML: flow and block styles, registries with a port in the image name, digest-pinned images, and both Windows and Unix line endings. A manifest that isn't valid YAML produces a calm error naming the offending line, not a blank screen.
Everything runs locally in your browser — the manifest never leaves your device, which matters when it references internal registries, namespaces or secret names you'd rather not paste into a cloud service. Copy the result, download it as a .txt file, or send it straight into another TextArray tool to continue working on it.
FAQ
Which Kubernetes resource kinds does it understand?
Any kind is listed by name, namespace and container count. Container details (images, resources, ports, volumes) are read from Pod, Deployment, StatefulSet, DaemonSet, ReplicaSet, Job and CronJob, since those are the kinds that carry a pod template.
Can I inspect a multi-document manifest?
Yes. Documents separated by "---" — the normal output of a Helm template or kustomize build — are all parsed and listed as separate resources.
What counts as a "latest tag" warning?
Both an explicit ":latest" tag and no tag at all, since Kubernetes itself treats a missing tag as "latest".
Does it validate the manifest against the Kubernetes API?
No. It reads the YAML structure to build the overview; it does not check the result against a cluster or a schema, so a resource can look complete here and still be rejected by the API server for other reasons.
Is my manifest uploaded anywhere?
No. Parsing and summarizing run entirely in your browser — your manifest, including any namespace, image or secret names it contains, never leaves your device.