DevOps Generators

K8s API Checker

All tools

A quick sanity check that a resource pairs its kind with a familiar apiVersion.

How it works

Four simple steps

1

Paste one resource

Include at least the apiVersion and kind lines.

2

Look up the pair

The checker compares them with its built-in list.

3

Read the status

Known common pair, or Unlisted with a prompt to verify.

4

Confirm on the cluster

Use kubectl api-resources for unlisted or custom kinds.

K8s API Checker

About K8s API Checker

An old Ingress copied from a blog post still says extensions/v1beta1, and the cluster rejects it after an upgrade. Before applying a manifest you did not write, it is worth confirming that the apiVersion and kind pair is one current clusters serve.

Paste a resource and the checker reads its first apiVersion and kind. If the pair is in a short built-in list it reports Known common pair; otherwise it says Unlisted and asks you to verify against your cluster version. The list covers 15 everyday kinds: Pod, Service, ConfigMap, Secret, Namespace, ServiceAccount and PersistentVolumeClaim under v1, Deployment, StatefulSet, DaemonSet and ReplicaSet under apps/v1, Ingress and NetworkPolicy under networking.k8s.io/v1, and Job and CronJob under batch/v1.

Unlisted does not mean wrong. HorizontalPodAutoscaler, PodDisruptionBudget, RBAC roles and every custom resource show as unlisted even when they are fine. Treat the result as a prompt, then confirm with kubectl api-resources on the target cluster. Only the first resource in the input is read, so check multi-document files one piece at a time, or list them first with the manifest inventory tool. If the YAML itself looks broken, run it through a YAML syntax validator.

The lookup is a small table inside the page, so no cluster access or upload is involved. Other Kubernetes and Git utilities live in the same category.

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.

The built-in list only covers core workload, networking and batch kinds. autoscaling/v2 is a valid group for autoscalers; it is simply not in the table. Verify kinds like that on your cluster.

No. It holds no version data. It only tells you whether the pair matches its list of current stable groups, so an old beta group shows as unlisted rather than with a removal release.

Only the first apiVersion and kind it finds are checked. Split the file or paste resources one at a time.

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 Manifest Splitter

Split multi-document YAML into one file per resource.

Open

Explore 321 free tools

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

Browse all tools