DevOps Generators

K8s Manifest Splitter

All tools

Turn one all-in-one manifest into clearly labeled chunks, one per resource.

How it works

Four simple steps

1

Paste the bundle

Add a multi-document YAML file with --- separators.

2

Split on separators

Each document is cut out and trimmed of blank edges.

3

Check the file names

Headers suggest kind-name.yaml for every section.

4

Create the files

Copy each section into its own file in your repo.

K8s Manifest Splitter

About K8s Manifest Splitter

Install guides often ship a single YAML file holding a dozen resources, but your GitOps repo keeps one object per file. Splitting by hand means hunting for separators and inventing names. This tool finds the boundaries and suggests a file name for each piece.

Each document between --- lines becomes its own section. Above it the splitter writes a header like ### file: deployment-api.yaml, built from the lowercased kind and the first name value in that document. Documents without a kind fall back to doc, and ones without a name use their position number.

The result is still one text output, not a set of separate downloads. Copy each section into its own file, or script the split using the ### file: markers as delimiters. Two things to check as you go: the name match takes the first name: it finds, so a container name can win if metadata comes later in the document, and two resources with the same kind and name in different namespaces get identical file names.

Nothing is uploaded, since the text is split in place by your browser. For a quick inventory before splitting, K8s Inspector lists every kind and name, and the YAML formatter tidies indentation in each new file. When the pieces are ready to template, K8s to Helm sketches a chart layout.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

No. The output is one text block with a ### file: header above each resource. Copy the sections out by hand or split on those headers with a short script.

The splitter uses the first name: line in the document. If metadata appears after the spec, the container name is found first. Move metadata to the top or rename the file yourself.

Yes. Everything between separators is copied as is, including comments. Only leading and trailing whitespace around each document is removed.

View more FAQs

Related tools

View all

Kubernetes Manifest Studio

Generate Deployment, Service, and Ingress YAML with a drift checklist.

Open

K8s Inspector

Summarize Kubernetes YAML kinds, names, and labels.

Open

K8s Resource Diff

Diff two Kubernetes manifests locally.

Open

K8s to Helm

Scaffold a Helm chart folder layout from pasted manifests.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools