Failed to load kubernetes config: invalid configuration: no configuration has been provided about kubescape HOT 11 CLOSED

@hermanbanken I think the issue in your case is that Kubescape loads the k8s config when the input is a file, loading the config is unnecessary since the input is a file and not a running cluster.
We will fix this next release :)

Cool! I was looking at the policyhandler package and couldn't figure out why it wasn't loading instead of getting the resources
https://github.com/armosec/kubescape/blob/571a15bee8de5a75beaee1aad091fcde2d7c25ca/policyhandler/handlenotification.go#L79-L84

Turned out it was aborting way before 😄

from kubescape.

@sundowndev I'm not sure what you are missing, is it possible you do not have a running Kubernetes cluster?

We use the client-go package for loading the Kubernetes config.

Please update if you managed to solve your issue

from kubescape.

@dwertent Not sure what I should specify in KUBERNETES_MASTER for it to work, I tried my kubeconfig path, my cluster's URL...

is it possible you do not have a running Kubernetes cluster?

No, I can manage my cluster with kubectl.

I think a better documentation about requirements and configuration would help me

from kubescape.

@sundowndev , if you don't mind, can you please share how your Kubernetes cluster is hosted? (minikube, EKS, GKE or etc.)

I am asking because for GKE support we needed to include an additional go module

from kubescape.

@BenHirschbergCa It's hosted on Digitalocean

from kubescape.

I have the same error, but I'm using plain YAML generated via Kustomize, eg.

cat output.dev.yaml        | kubescape scan framework nsa -
cat output.test.yaml       | kubescape scan framework nsa -

from kubescape.

@hermanbanken I think the issue in your case is that Kubescape loads the k8s config when the input is a file, loading the config is unnecessary since the input is a file and not a running cluster.

We will fix this next release :)

from kubescape.

@hermanbanken I fixed the issue, please confirm it works :)

from kubescape.

@sundowndev try setting export KUBECONFIG=<path to config>, is it better?

from kubescape.

@sundowndev try setting export KUBECONFIG=<path to config>, is it better?

yep that's it, I confused KUBE_CONFIG_PATH and KUBECONFIG, thanks

from kubescape.

Verified it works, thanks!

from kubescape.