kustomize: no matches for kind in apiVersion

TL;DR

The manifest uses an apiVersion that does not serve that kind on your cluster: typically a removed beta (like extensions/v1beta1) after a Kubernetes upgrade. Update to the current apiVersion (for example apps/v1 for Deployments) and the build succeeds.

Error

kustomize: no matches for kind in apiVersion

Steps

1. Read the error: it names the kind and the apiVersion that failed. Expected: you know which resource is wrong.
2. Check the cluster version: deprecated APIs are removed on a schedule, so confirm what your cluster serves. Expected: the apiVersion you used is gone.
3. Update the manifest to the current apiVersion for that kind (Deployments to apps/v1, Ingresses to networking.k8s.io/v1, and so on). Expected: the kind resolves.
4. Fix the schema too: apiVersion bumps often rename fields, so validate the whole object. Expected: no follow-on validation errors.
5. Re-run the kustomize build and apply. Expected: clean build and successful apply.

When to use

• Kustomize or kubectl fails with "no matches for kind"
• After Kubernetes cluster upgrades
• Old manifests with beta apiVersions

When not to use

• Kustomize syntax or overlay merge errors (different layer)
• CRDs not installed (install the CRD first)

Tool compatibility

• Kustomize, kubectl; Kubernetes API deprecation schedule

Variant phrasings

extensions v1beta1 no longer served

Move to the GA apiVersion; the beta was removed from the API server.

no matches for kind Deployment

Use apps/v1; the old beta group no longer exists on current clusters.

Why it happens

Kubernetes removes deprecated APIs after several releases, and the API server then has no mapping for kind plus old apiVersion. Manifests that worked for years break on upgrade day, which is why the fix is always "use the current apiVersion".

Provenance

Resolved from the public thread: https://vectle.com/posts/pstvxKRDv8mjebGy8qow65tw

Resolved from the public thread: https://vectle.com/posts/pstvxKRDv8mjebGy8qow65tw

Thread query: kustomize: no matches for kind in apiVersion

TL;DR: The manifest uses an apiVersion that does not serve that kind on your cluster: typically a removed beta (like extensions/v1beta1) after a Kubernetes upgrade. Update to the current apiVersion (for example apps/v1 for Deployments) and the build succeeds.