YAML to JSON for Kubernetes — Convert K8s Manifests Free Online

Kubernetes manifests are written in YAML, but the Kubernetes API works internally in JSON. Converting between the two formats is a daily task for DevOps engineers debugging live cluster state, reconciling source YAML with kubectl output, or feeding manifests to tools that expect JSON input.

The fastest way to convert a Kubernetes YAML manifest to JSON: paste it into the free browser converter, click Convert. No kubectl, no cluster access, no package installation needed. For automation, kubectl has a built-in output flag that returns live resource state as JSON.

Convert Kubernetes YAML to JSON in Your Browser

Open the YAML to JSON converter and paste your Kubernetes manifest. Click Convert. Every standard K8s resource type works:

• Deployments — app deployment specs with containers, replicas, strategy
• Services — ClusterIP, NodePort, LoadBalancer service definitions
• ConfigMaps — key-value config data in YAML block format
• Pods — individual pod specs
• StatefulSets, DaemonSets, Jobs, CronJobs
• Ingress and NetworkPolicy resources
• kubeconfig files — cluster connection configs
• Helm values.yaml files

The converter handles YAML anchors and aliases, which Kubernetes does not use natively but which appear in Helm templates and some operator configs. Multiline string values (using YAML block scalars | or >) are preserved correctly in the JSON output.

Using kubectl to Get Kubernetes Resources as JSON

If you have kubectl access to a cluster, you can get live resource state in JSON directly:

# Get a deployment as JSON
kubectl get deployment my-app -o json

# Get a service as JSON
kubectl get service my-service -o json

# Get all pods in a namespace as JSON
kubectl get pods -n my-namespace -o json

# Convert a local YAML file to JSON (dry-run)
kubectl apply -f manifest.yaml --dry-run=client -o json

The last command is particularly useful: it converts your local YAML file to JSON without applying it to the cluster. This shows exactly what the Kubernetes API would receive, including defaulted fields and normalized structure.

Compare the dry-run JSON output against your source YAML to understand what the API adds (resource versions, default labels, annotations) vs what you defined.

Sell Custom Apparel — We Handle Printing & Free Shipping

Why Kubernetes Engineers Convert Between YAML and JSON

The most common reasons DevOps engineers need YAML-to-JSON conversion for Kubernetes work:

Debugging with jq: jq is a JSON processor — it cannot read YAML directly. Convert a manifest to JSON first, then pipe through jq to extract specific fields: kubectl get deployment my-app -o json | jq '.spec.template.spec.containers[].image'

Postman/API testing: The Kubernetes REST API accepts JSON. If you are making direct API calls to test admission webhooks or custom controllers, you need the manifest in JSON format.

Comparing source vs live state: Your source manifest is YAML. kubectl get -o json returns live state. Converting both to JSON lets you use a diff tool to see exactly what changed (annotations, status fields, defaulted values).

Terraform and Pulumi: Some infrastructure-as-code tools that manage Kubernetes resources expect JSON input. Converting YAML to JSON is a common interop step.

Converting kubeconfig Files from YAML to JSON

kubeconfig files are YAML by default and contain cluster credentials, context definitions, and user authentication data. Converting a kubeconfig to JSON is useful for:

• Passing cluster credentials to tools that expect JSON config
• Inspecting the structure of a kubeconfig programmatically
• Debugging connection issues by seeing all fields clearly

Important security note: kubeconfig files contain authentication tokens and certificates. The browser converter processes everything locally in your browser — nothing is uploaded to any server. Use the browser tool rather than a third-party online converter that might log your credentials.

After conversion, treat the resulting JSON with the same security care as the original YAML — do not paste it into public forums or commit it to version control without redacting the credentials.

Frequently Asked Questions

How do I convert a Kubernetes YAML manifest to JSON?

Two options: (1) Paste the YAML into the free browser converter and click Convert. (2) Use kubectl: kubectl apply -f manifest.yaml --dry-run=client -o json to convert without applying to the cluster. Both produce valid JSON.

Why does Kubernetes use YAML if the API uses JSON internally?

Kubernetes accepts both YAML and JSON, but YAML became the community standard for manifest files because it is more readable and supports comments. kubectl converts YAML to JSON before sending it to the API server — you can see this with the --dry-run=client -o json flag.

Can I convert a kubeconfig file to JSON safely?

Yes, if you use the browser-based converter — it processes everything locally in your browser and does not upload your data to any server. Avoid online tools that upload files to a server, as kubeconfig files contain authentication credentials.

How do I convert YAML to JSON for use with jq?

jq requires JSON input. Convert your YAML to JSON first using the browser tool or kubectl, then pipe through jq. For live cluster resources: kubectl get deployment my-app -o json | jq ".spec.replicas"