Closed mcbenjemaa closed 11 months ago
\"https://10.10.10.35:6443/api?timeout=10s\": dial tcp 10.10.10.35:6443: connect: connection refused"
control plane endpoint doesn't function
2023-08-16T14:09:49Z INFO controllers.TalosControlPlane bootstrap failed, retrying in 20 seconds {"namespace": "default", "talosControlPlane": "proxmox-test-control-plane", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate signed by unknown authority\""}
your Talos instance most probably didn't get the machine config via user-data as it should in CAPI world.
thanks for closing the issue
There is nothing for the CACPPT here, as if the problem is, it's around either Talos or infrastructure provider.
I tried to use metal-iso to set talos-config But it doesn't work.
I think the only way, if the control provider allow insecure via a flag or something
This is not how CAPI works, infrastructure provider should submit already prepared machine config as user-data to the instance. There's no other way supported with CAPI atm.
Can you provide an example of userdata for talos?
It's the machine config. CAPI when working correctly does it for you, there's nothing related to this particular issue or repository.
Hey,
I'm trying to use cacppt as controlplane provider to bootrap cluster in Proxmox, I provided the nocloud image to the VM.
But when I apply my resources, cacppt is complaining about certifacates.
Logs
Note, I'm setting a static ip via proxmox API.
but, this fails.