No resources found ☸️ Kubernetes

No resources found in default namespace

Not an error: kubectl found nothing of that kind in the namespace it looked in — usually because the resources are in another namespace.

Seen on: Kubernetes

Meaning

kubectl uses the namespace from your current context (often default). Workloads installed by Helm or operators live in their own namespaces. It can also mean you’re on the wrong cluster context.

Common causes

  • Resources are in another namespace
  • Wrong cluster/context
  • Label selector matches nothing
  • Resources really were deleted

⚡ Quick fix

  1. Search all namespaces: kubectl get pods -A
  2. Set the namespace: -n app or kubectl config set-context --current --namespace=app
  3. Check the context

Detailed fix by platform

Kubernetes

  1. bash
    kubectl get pods -A | grep web
kubectl config set-context --current --namespace=app

How to diagnose

  1. Namespace — kubectl config view --minify | grep namespace
  2. Context — kubectl config current-context
  3. Selector — Labels correct?

🔧 Still not fixed?

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

🧠 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.