no context is set

[yamikeigo]

Hello. I'm trying to setup Talos on a Proxmox VM following the method outlined below:
https://www.youtube.com/watch?v=YdQCeU7NOak&pp=ygUNdGFsb3MgaW5zdGFsbA%3D%3D

I went step for step and everything went fine up to: export TALOSCONFIG="_out/talosconfig"

I then enter this command: talosctl config endpoint $CONTROL_PLANE_IP

and I get 'no context is set'

I tried going through the possible commands via -h, but nothing worked

I then looked at the guide from the Sidero Labs channel and they talk about actually installing to the disk but the 'talos get disks' command won't work after I deploy the initial 'apply-config' command

perhaps some syntax was updated the way 'talosctl disks' was deprecated?

[rothgar]

does your _out/talosconfig file have multiple contexts listed? Is there anything in that file?

[yamikeigo]

this is what I see in that file:

context: talos-proxmox-cluster
contexts:
talos-proxmox-cluster:
endpoints: []
ca: alkdjflakdjZ==
crt: lakdjlfakjdf=
key: a;lkdfja;lkdl;akjdf

[yamikeigo]

of course it's indented to some degree and I've omitted the sensitive data, but I'm sure you get the gist

@rothgar do I have to include 'talos-proxmox-cluster' in the command somewhere as part of the syntax? is that it?

[steverfrancis]

Just try accessing the talosconfig file directly.
talosctl -e $CONTROL_PLANE_IP -n $CONTROL_PLANE_IP health --talosconfig=_out/talosconfig

[yamikeigo]

@steverfrancis

from your suggestion I get:

error constructing client: failed to create client connection: failed to resolve configuration context: talos config file is empty

is there anything I'm missing? this is just 2 Proxmox VMs on the same LAN with network connectivity confirmed. would it be something in my environment? I don't believe I have anything exotic going on

[steverfrancis]

THis is nothing to do with the fact its proxmox (I dont think), and just basic talos access.
You jsut need to find the talosconfig file that was generated when you did the talosctl gen config, and use that in the command I specified.
See in general https://www.talos.dev/v1.9/introduction/getting-started/#configure-talos-linux

[yamikeigo]

@steverfrancis I will tinker with the config file. can't do anything worse to it I guess. I guess I'm just left wondering why my situation is so off-track from the documentation if the gen config command is supposed to spit out the same thing for everyone? it is supposed to spit out the same thing for everyone, no? or is it a function of the the talosctl pkg that I have installed on my Debian server?

[yamikeigo]

ok so I went into the talosconfig file and inputted the control plane endoint into the empty brackets, then my worker node finally showed as 'worker' in the 'Type' section where before it did not. Not sure if I'm now supposed to continue with the process and input talosctl bootstrap but I get the following error when I try error constructing client: failed to determine endpoints and I can no longer get back into the _out folder as I get permission denied, which I assume has to do with the API security being set?

[yamikeigo]

I have some spare NUCs lying around. I guess I'll try that. Kind of a bummer that this proxmox method is being ornery. Oh well

[yamikeigo]

so this is where I'm currently at:

I tried the following 3 commands on a spare NUC I have...

talosctl gen config mycluster https://192.168.0.2:6443
talosctl -n 192.168.0.2 get disks --insecure
talosctl apply-config --insecure -n 192.168.0.2 --file controlplane.yaml

However, with the 'get disks' command I ran into the problem that talosctl could not detect or output the hardisk on the NUC, for some reason. I used gparted to acquire the name of the disk and ran the next command, but that didn't go well, but at least I could see that it communicated something.

so now that I have 3 commands that I know that work, I tried usint them back onto my Proxmox setup, but when shooting the 'get disks' command over to the Proxmox CP I get the following error:

rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: remote error: tls: certificate required"

I think this speaks to something in my environment, but I have no idea what it is, because Talos documentation says all that should be needed for prerequisites is network access

Edit: I got a better look at the block device scheme and it looks like the hard disk for this NUC is MMC/SD instead of the conventional SCSI. Is it possible that Talos would have an issue with that?

[yamikeigo]

not that anyone is paying attention lol. kind of self-documenting my steps here.

I moved on to a more conventional miniPC and was able to get through the steps for bare metal install. Now I need to learn how to add a worker node since I don't want to do the step where I allow nodes on the CP

seems I had to download the kubeconfig file, then install the kubectl command in order to be able to properly run the kubectl get nodes command

also the k get no command is probably deprecated? since that command was not recognized

docs don't really speak to that, but I guess there's tons and tons of variables for all this so that might be a challenge

[yamikeigo]

@rothgar @steverfrancis

I think I figured something out. Perhaps it's unique to my setup, not sure why, but it seems like with my environment it did not like the talosctl -n 192.168.0.2 get disks --insecure command. Again, I get rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: remote error: tls: certificate required" as a result of that command. I asked GPT for help, and it didnt' really provide any insight. It just pointed to some kind of communication issue, but I'm not sure what that would be at this point since the --insecure command is supposed to get around that and the VM is pingable. In any case, if we just assume that any conventinal VM is going to be using /dev/sda, which they susually will, you can simply proceed with the apply-config command and it works to some extent. It communicates to some degree but now hangs at the Booting state with some error about a "proxy" preventing a connection. I have no idea what that would be. I have no proxy set up that I'm aware of. Any breadcrumbs are appreciated...

[yamikeigo]

ok wow I think I got this to work. I had to fumble through it because the sequence no longer matches any tutorials/documentation currently in existence (at least for me it didn't), but I think it's all good now. Now I have to actually learn k8s lol