Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting ConfigInferenceExhausted #6

Open
Dentrax opened this issue Jan 15, 2021 · 1 comment
Open

Getting ConfigInferenceExhausted #6

Dentrax opened this issue Jan 15, 2021 · 1 comment

Comments

@Dentrax
Copy link

Dentrax commented Jan 15, 2021

I'm getting ConfigInferenceExhausted error with macOS. I do not know what that means exactly, and what it needs.

$ suspicious-pods --version

suspicious-pods 1.1.0
$ KUBECONFIG=/Users/furkan/.kube/config-foo suspicious-pods

Error: Kubeconfig(ConfigInferenceExhausted { cluster_env: Kubeconfig(MissingInClusterVariables { hostenv: "KUBERNETES_SERVICE_HOST", portenv: "KUBERNETES_SERVICE_PORT" }), kubeconfig: Kubeconfig(LoadContext { context_name: "kubernetes-admin@prod-foo" }) })
$ KUBECONFIG=/Users/furkan.turkal/.kube/config-foo kubectl get --raw='/readyz?verbose'

All is OK.

$ KUBECONFIG=/Users/furkan.turkal/.kube/config-foo kubectl cluster-info

All is running.

$ KUBECONFIG=/Users/furkan.turkal/.kube/config-foo kubectl get pods

Success.
@davidB
Copy link

davidB commented Jan 28, 2021

This error means that the context kubernetes-admin@prod-foo define as current context is not defined into the loaded kubeconfig.
Does the context fully (user & server) defined into the file /Users/furkan.turkal/.kube/config-foo ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants