talos
talos copied to clipboard
Hyper-V Setup according to manual fails.
Dear Sirs,
im trying , the 1st time in my life, to setup a kubernetes cluster, utilizing talos.
Im following the guide
This seems to work until:
talosctl apply-config --insecure --nodes $CONTROL_PLANE_IP --file .\controlplane.yaml
This command seems to be not successful.
When the machined restarts i end up , it looks like, a non working api on port 6443.
I have multiple error messages which ends up like connect: connection refused
.
Environment:
HYPER V 2016 talos-amd64.iso from release 1.22 utilizing a existing network with a active dhcp server.
Screenshot with some output
My ultimate goal is to to setup kubernetes cluster for ci/cd usage, and tests. I do not have any pervious expierence with kubernetes. My Idea was that stuff like k3os, or talos would give me a easy and trimmed down approach.
It looks like you missed the 'Bootstrap' step probably: https://www.talos.dev/v1.2/talos-guides/install/virtualized-platforms/hyper-v/#bootstrap-cluster****
that is accorrding to the document the last step. After
- Pushing Config to the Nodes
i start to get errors,
the following commands then fail.
The logs you provided probably mean that there was no bootstrap issued. If you had other errors running bootstrap, let's talk about them. But without bootstrap the cluster will never come up.
So you suggest that the order of commands in the documentation https://www.talos.dev/v1.2/talos-guides/install/virtualized-platforms/hyper-v/#bootstrap-cluster
is wrong ?
Maybe i was not clear enough, at the mentionend state i start getting erros, the follow up command gives me errors as well. The commands later one, just return missing context, whatever that should mean
Probably you should also read generic intro https://www.talos.dev/v1.2/introduction/getting-started/ to understand the common concepts.
The Hyper-V guide is missing some steps, probably you need to run talosctl config merge ./talosconfig
to merge talosconfig
generated for your cluster into default talosconfig
search path.
Thanks i will try
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.