Open Geethree opened 5 months ago
This might be a valid issue now with talosctl
1.7.x, as it changed the way ports are exposed. I guess it comes from Sidero Metal docs. Please check with that 8081 is exported correctly on the host, if it does, we can simply update Sidero Metal docs to drop the endpoint
.
@smira when you say 'Please check with that 8081 is exported correctly on the host', what exactly do you mean? I've just upgraded talosctl from a 1.6.x release to the latest 1.7 and I'm now seeing this issue too - my cluster create command does expose 8081 already though:
; talosctl cluster create --name sidero-bootstrap \
-p 69:69/udp,8081:8081/tcp,51821:51821/udp --workers 0 --config-patch \
'[{\"op\": \"add\", \"path\": \"/cluster/allowSchedulingOnMasters\", \"value\": true}]' \
--endpoint 172.25.100.2 --nameservers 10.101.0.2,10.101.0.3 \
--docker-host-ip 172.25.100.2 --memory 6144
Is this not the correct way of exposing the port?
I mean try dropping --endpoint
argument, use docker
CLI to inspect how ports are exposed, if there's a bug there, please report an issue.
When following the sidero getting started to bring up a cluster with:
Where it states that the
HOST_IP
should be the IP address of my workstation which I included above. When I do this, the tooling hangs here:It seems like etcd isn't coming up
I've debugged this to the
--endpoint
flag. If I don't set this, a cluster comes up.Any thoughts on what is going on here?
talosctl v1.7.4 docker 25.0.2