Closed lpellegr closed 13 hours ago
I am getting the same error with version 0.3.0 which was working a few weeks ago.
The firewall rules seems OK for my IP address. Not sure what the issue is.
Using node types with only 2 GB of RAM for Control Plane nodes is quite risky. A blank CP node alone typically requires 1.5 to 2 GB of memory just for the OS and Kubernetes system daemons. Blank Worker nodes typically need less resources between 0.5 and 1 GB. If you have the metrics server installed (it is by default), you can verify memory usage using kubectl top nodes
. While I can't say for certain this is causing your issue, it’s worth investigating.
Have you checked the cluster status and ensured etcd is healthy? You can run talosctl health
and refer to the troubleshooting docs for guidance.
Additionally, you can review the Talos dashboard through the Hetzner Cloud Console. Go to your Hetzner Cloud project, open the "Console" for your control plane nodes, and check the node status. A healthy node should look like this:
If your cluster appears healthy and there are no obvious issues, it’s worth considering potential network-related problems.
Thank you so much for your assistance! As you pointed out, the issue was indeed caused by insufficient memory. After upgrading to a higher VM capacity with 4GB of memory for the control planes, everything started working seamlessly.
Using version 0.6.3, cluster deployment gives:
Here is the configuration file used: