doesn't have a resource type Kubernetes Origin: Platform & cloud Last updated 13 Oct 2026

error: the server doesn't have a resource type "x"

kubectl doesn’t know the resource name you typed — a typo, a CRD that isn’t installed, or a stale discovery cache.

Exact message you may see the server doesn't have a resource typedoesn't have a resource type
Explore the map of this error Full error map →
Seen on: Kubernetes

Meaning

Resource names come from API discovery. Custom resources appear only after their CRD is installed, and kubectl caches discovery in ~/.kube/cache, so freshly installed CRDs may need a cache refresh.

Common causes

  • Typo or wrong short name
  • CRD/operator not installed on this cluster
  • Stale discovery cache
  • Wrong cluster context

⚡ Quick fix

  1. List types: kubectl api-resources | grep -i name
  2. Install the CRD/operator
  3. Clear the cache: rm -rf ~/.kube/cache

Detailed fix by platform

Kubernetes

  1. bash
    kubectl api-resources | grep -i cert
rm -rf ~/.kube/cache/discovery

How to diagnose

  1. Types — kubectl api-resources
  2. Context — Right cluster?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

AlreadyExists — Error from server (AlreadyExists): ... already exists (Kubernetes)AlreadyExistsForbidden — Error from server (Forbidden): pods is forbidden: User "x" cannot list resource "pods" in API group "" in the namespace (Kubernetes)Forbiddengke-gcloud-auth-plugin not found — kubectl: error: executable gke-gcloud-auth-plugin not found — it looks like you are trying to use a client-go credential plugin that is not installed (Google Cloud / Firebase)gke-gcloud-auth-plugi…is waiting to start — Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating (Kubernetes)is waiting to startkubectl connection refused — kubectl: The connection to the server localhost:8080 was refused — did you specify the right host or port? (Kubernetes)kubectl connection re…no matches for kind — no matches for kind "Ingress" in version "extensions/v1beta1" (resource mapping not found) (Kubernetes)no matches for kindNotFound — Error from server (NotFound): deployments.apps "x" not found (Kubernetes)NotFoundx509 (kubectl) — Unable to connect to the server: x509: certificate has expired or is not yet valid / certificate signed by unknown authority (Kubernetes)x509 (kubectl)doesn't h…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.