on 2023 Dec 17 2:50 PM
Hi All,
I have installed kubectl CLI in Windows 10 Laptop and installed kubelogin. I followed all steps mentioned in setting and configuring kubectl for Kyma tutorial in Discovering Kubernetes .
After installing KubeConfig file in ./kube folder when i try to run
kubectl cluster-info am getting below error
E1217 20:09:08.178329 7056 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
E1217 20:09:08.181377 7056 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
E1217 20:09:08.184684 7056 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
E1217 20:09:08.185733 7056 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
E1217 20:09:08.186730 7056 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
I am using trail SAP BTP account. Please help me to resolve this issue. Thanks in advance.
Request clarification before answering.
Hey,
are you sure your Kubernetes config file is in the right place?
Should be
<HOME OR USER DIRECTORY>/.kube/configIt looks like kubectl is trying to connect to a local Kubernetes instance.
Try something like
kubectl config get-contextsTo see if your Kubernetes context shows up and is actually the default context.
Otherwise you could also use
kubectl --kubeconfig <PATH TO YOUR CONFIG FILE> ...if you do not wish to use your global config file.
Best regards,
Marcus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 6 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.