Kubectl get nodes return "the server doesn't have a resource type "nodes""

user_1122891 0
Viewed 33753

I installed the Kubernetes and performed kubeadm init and join from the worker too. But when i run kubectl get nodes it gives the following response

the server doesn't have a resource type "nodes"

What might be the problem here? COuld not see anything in the /var/log/messages

Any hints here?

kubectl kubernetes
3 Answers

In my case, I wanted to see the description of my pods.

When I used kubectl describe postgres-deployment-866647ff76-72kwf, the error said error: the server doesn't have a resource type "postgres-deployment-866647ff76-72kwf".

I corrected it by adding pod, before the pod name, as follows:

kubectl describe pod postgres-deployment-866647ff76-72kwf
user_146193830

I got this message when I was trying to play around with Docker-Desktop. I had previously been doing a few experiments with Google Cloud and run some kubectl commands for that. The result was that in my ~/.kube/config file I still had stale config related to a now non-existent GCP cluster, and my default k8s context was set to that.

Try the following:

# Find what current contexts you have
kubectl config view

I get:

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: DATA+OMITTED
    server: https://kubernetes.docker.internal:6443
  name: docker-desktop
contexts:
- context:
    cluster: docker-desktop
    user: docker-desktop
  name: docker-desktop
current-context: docker-desktop
kind: Config
preferences: {}
users:
- name: docker-desktop
  user:
    client-certificate-data: REDACTED
    client-key-data: REDACTED

So only one context now. If you have more than one context here, check that its the one you expect that is set to current-context. If not change it with:

# Get rid of old contexts that you don't use 
kubectl config delete-context some-old-context

# Selecting the context that I have auth for
kubectl config use-context docker-desktop
user_8139190
Related