kubectl get nodes

[yamikeigo]

I seem to have succeeded with all of the initial setup steps, but still seeing some irregularities. This is what I get when I run kubectl get nodes:

user@2-debiandev-vm:/usr/bin$ kubectl get nodes
E0224 14:31:45.907943    3895 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E0224 14:31:45.909466    3895 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E0224 14:31:45.910906    3895 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E0224 14:31:45.912412    3895 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E0224 14:31:45.913899    3895 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
The connection to the server localhost:8080 was refused - did you specify the right host or port?
user@2-debiandev-vm:/usr/bin$ kubectl config current-context
error: current-context is not set
user@2-debiandev-vm:/usr/bin$ kubectl config view
apiVersion: v1
clusters: null
contexts: null
current-context: ""
kind: Config
preferences: {}
users: null

I did not deviate from any of the steps. CP and WN are in a healthy and running state. I run the dashboard and health commands and they return outputs successfully. I assume I have to get this to NOT point to that localhost address? but I'm uncertain how/where I do that.

[rothgar]

It doesn't look like you downloaded the kubeconfig from the cluster. Try talosctl kubeconfig -e $ENDPOINT to download the configuration.

[yamikeigo]

you're not incorrect, but there's a bit more to this that has me thoroughly confused:

firstly, the command you suggested does not work. As a result I get:
error constructing client: failed to create client connection: failed to resolve configuration context: talos config file is empty

what DOES work, however, is this command:
talosctl --nodes <ipadd> --endpoints <ipadd> --talosconfig ./talosconfig kubeconfig ./kubeconfig

with that command, it then seems that my kubectl is responsive. such as when I enter kubectl get nodes, I get the following:

NAME         STATUS   ROLES           AGE     VERSION
taloscp-01   Ready    control-plane   5h36m   v1.32.2
taloswn-01   Ready    <none>          5h36m   v1.32.2

I reached out to a kubernetes discord channel about this whole scenario and why the WORKER node is not being listed as "worker" they told me that I'm "hacking things rather than learning" and that by default my correct kubeconfig file should be in my home as .kube/config, but when I go to that location no such directory and file exists. They also suggested that I move to something simpler for now, like microk8s. I'm just here trying to understand why some commands work while others don't, but ultimately yeah, it's probably too much for right now.