I had exactly the same problem even after having correct config (by running an azure cli command).

It seems that kubectl expects HOME env.variable set but it did not exist for me. There is however a solution:

If you add a KUBECONFIG environmental variable that will point to config it will start working.

Example:

setx KUBECONFIG %UserProfile%\.kube\config

When the variable is present kubectl has no troubles reading from file.

P.S. It is an alternative to setting a HOME variable as suggested in another answer.

If you can see that your config file is correctly configured by going to $HOME/.kube/config - Linux or %UserProfile%/.kube/config - Windows but you are still receiving the error message - try running command line as an administrator.

More information on the config file can be found here: https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/

For me it appeared to be due to Windows not having a HOME environment variable set. According to the docs kubectl will use the config file $(HOME)/.kube/config. But since this variable isn't set on Window it can't locate the file.

I created a HOME variable with the same value as USERPROFILE and it started working.

I was facing the same error while firing the command "kubectl get pods"

The issue has been resolved by having following steps below:

a) First find out current-context

kubectl config get-contexts
CURRENT   NAME      CLUSTER   AUTHINFO   NAMESPACE

b) if no context is set then set it manually by using

kubectl config set-context <Your context>

Hope this will help you.

I'm using Hyper-V on Local Windows and I met this error because I didn't configure minikube.

(I know the question is about Azure, not minikube. But this article is on the top for the error message. So, I've put the solution here.)

1. enable Hyper-V.

Type in systeminfo on your Terminal. If you can find the line below,

Hyper-V Requirements:     A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Hyper-V works correctly.

If you can't, enable it from settings.

2. Create Hyper-V Network Switch

Open Hyper-V manager. (Searching it is the fastest way.)

Next, click your PC name on the left.

Then, you can find Virtual Switch Manager menu on the right.

Click it and choose External Virtual Switch with name: "Minikube Switch"

Click apply to create it.

3. start minikube

Go back to terminal and type in:

minikube start --vm-driver hyperv --hyperv-virtual-switch "Minikube Switch"

For more information, check the steps in this article.