#356 · Developer Tool

Kubernetes Resource Extractor

Build an inventory from a bundle of Kubernetes manifests without applying anything to a cluster. The extractor reads multi-document YAML and lists API version, kind, namespace, name, replica count, container count, and selected workload details. Export the normalized rows as JSON or CSV for review notes, migration planning, or a lightweight manifest catalog.

Developer Input

YAML or line input

Ad space

How to use this developer tool

  1. Paste the requested YAML or key/value input.
  2. Adjust the available options for the target output.
  3. Select Extract Resources or press Ctrl/Cmd + Enter.
  4. Review findings, then copy or download the result.

What this developer tool does

Converts each Kubernetes YAML document into a normalized resource row and groups the summary by kind and namespace.

Namespace defaults to default for namespaced-looking resources when metadata.namespace is absent. List resources are expanded when an items array is available.

The result is generated locally and should be reviewed before deployment.

Example

The Sample button loads a representative input. Running it produces the same structured output displayed in the result panel, including counts and any findings.

apiVersion: v1
kind: Service
metadata:
  name: web
  namespace: production
spec:
  type: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
  namespace: production
spec:
  replicas: 3

Use cases

  • Pre-commit configuration review
  • Pull request documentation
  • Migration inventory preparation
  • Training and troubleshooting

Tips for reliable output

  • Use spaces instead of tab indentation in YAML.
  • Keep multi-document separators on their own line.
  • Review generated files before applying them.
  • Confirm static findings with official CLI validation.
  • Avoid pasting production secrets into shared devices.

Processing details

Namespace defaults to default for namespaced-looking resources when metadata.namespace is absent. List resources are expanded when an items array is available.

Cluster-scoped versus namespaced behavior is inferred, not discovered from a live API server. Generated resources and remote Kustomize bases are not included.

Frequently asked questions

Can the extractor read a multi-document Kubernetes YAML bundle?

The result follows the static rules described on this page. Review finding 1 in context and confirm it with the relevant Docker or Kubernetes command before deployment.

How is a missing Kubernetes namespace represented?

The result follows the static rules described on this page. Review finding 2 in context and confirm it with the relevant Docker or Kubernetes command before deployment.

Are List kind items expanded into separate resource rows?

The result follows the static rules described on this page. Review finding 3 in context and confirm it with the relevant Docker or Kubernetes command before deployment.

Does the resource inventory include container images and replica counts?

Input is processed in your browser. The page does not make a network request with the configuration, but downloaded output and browser history should still be handled according to your security policy.

Can I export the Kubernetes resource inventory to CSV?

The result follows the static rules described on this page. Review finding 5 in context and confirm it with the relevant Docker or Kubernetes command before deployment.