silly-fish-63272
04/21/2023, 3:36 PMGreetings, well I just toasted my third machine using a combo of k3d, kubectl, and docker. Our system was working GREAT for several weeks and, after, we think, deploying (deleting, re-building, re-deploying cluster/pods) too many times (we are testing for deployment to various machines), we eventually start seeing this error: E0421 10:43:09.559285 5185 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp 127.0.0.1:8080: connect: connection refused. On all three of the toasted machines (and by toasted I mean we can no longer get the application working and always get the above error), we totally a) pruned all docker imates; b) deleted K3D cluster; c) deleted k3d; d) deleted docker; then re-installed k3d and docker fresh. Same error occurs, though. Been there done that with Googling, it does seem to be related to too many re-deployments, but after deleting and re-installing the k3d and docker packages, we're up against a wall. Any thoughts?
rough-farmer-49135
04/21/2023, 3:55 PMsilly-fish-63272
04/21/2023, 4:07 PMcreamy-pencil-82913
04/21/2023, 4:11 PM<http://localhost:8080>
it almost always means that you forgot to use a kubeconfig file, and it’s falling back to the default server address. K3s will always use https and port 6443.silly-fish-63272
04/21/2023, 5:07 PMcreamy-pencil-82913
04/21/2023, 5:08 PMsilly-fish-63272
04/21/2023, 5:10 PMcreamy-pencil-82913
04/21/2023, 5:10 PMsilly-fish-63272
04/21/2023, 5:14 PMLast login: Fri Apr 21 12:31:31 2023 from 172.16.15.11
itng@tmc1:~$ kubectl get events
E0421 13:05:13.670109 5769 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp 127.0.0.1:8080: connect: connection refused
E0421 13:05:13.670910 5769 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp 127.0.0.1:8080: connect: connection refused
E0421 13:05:14.157934 5769 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp 127.0.0.1:8080: connect: connection refused
E0421 13:05:14.159035 5769 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp 127.0.0.1:8080: connect: connection refused
E0421 13:05:14.160043 5769 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp 127.0.0.1:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?
creamy-pencil-82913
04/21/2023, 5:18 PMsilly-fish-63272
04/21/2023, 5:58 PMcreamy-pencil-82913
04/21/2023, 6:08 PMkubectl config view -v=6
to see the current kubeconfig and where it’s coming from~/.kube/config
silly-fish-63272
04/21/2023, 6:43 PM